Skip to main content

The full table of contents of the book High Performance in-memory computing with Apache Ignite

The book High Performance in-memory computing with Apache Ignite has been completed and available at LeanPub.


Table of contents:

  • Introduction
    • What is Apache Ignite
    • Who uses Apache Ignite
    • Why Ignite instead of others
    • Our Hope
  • Chapter one: Installation and the first Ignite application
    • Pre-requirities
    • Installation
    • Run multiple instances of Ignite in a single host
    • Configure a multi-node cluster in different host
    • Rest client to manipulate with Ignite
    • Java client
    • SQL client
    • Conclusion
    • What's Next
  • Chapter two: Architecture overview
    • Functional overview
    • ClusterTopology
      • Client and Server
      • Embedded with the application
      • Server in separate JVM (real cluster topology)
      • Client and Server in separate JVM on single host
    • Caching Topology
      • Partitioned caching topology
      • Replicated caching topology
      • Local mode
    • Caching strategy
      • Cache-aside
      • Read-through and Write-through
      • Write behind
    • Data model
    • CAP theorem and where does Ignite stand in?
    • Clustering
      • Cluster group
      • Data collocation
      • Compute collocation with Data
      • ZeroSPOF
    • How SQL queries works in Ignite
    • Multi-data center replication
    • Asynchronous support
    • Resilience
    • Security
    • KeyAPI
    • Conclusion
    • What's next
  • Chapter three: In-memory caching
    • Apache Ignite as a 2nd level cache
      • MyBatis 2nd level cache
      • Hibernate 2nd level cache
    • Java method caching
    • Web session clustering with Apache Ignite
    • Apache Ignite as a big memory, off-heap memory
    • Conclusion
    • What’s next
  • Chapter four: Persistence
    • Persistence Ignite’s cache
      • Persistence in RDBMS (PostgreSQL)
      • Persistence in MongoDB
    • Cache queries
      • Scan queries
      • Text queries
    • SQL queries
      • Projection and indexing with annotations
      • Query API
      • Collocated distributed Joins
      • Non-collocated distributed joins
      • Performance tuning SQL queries
    • Apache Ignite with JPA
    • Expiration & Eviction of cache entries in Ignite
      • Expiration
      • Eviction
    • Transaction
      • Ignite transactions
      • Transaction commit protocols
      • Optimistic Transactions
      • Pessimistic Transactions
      • Performance impact on transaction
    • Conclusion
    • What’s next
  • Chapter five: Accelerating BigData computing
    • Hadoop accelerator
      • In-memory Map/Reduce
      • Using Apache Pig for data analysis
      • Near real-time data analysis with Hive
      • Replace HDFS by Ignite In-memory File System (IGFS)
      • Hadoop file system cache
    • Ignite for Apache Spark
      • Apache Spark – an introduction
      • IgniteContext
      • IgniteRDD
    • Conclusion
    • What’s next
  • Chapter six: Streaming and complex event processing
    • Introducing data streamer
      • StreamReceiver
      • StreamVisitor
    • IgniteDataStreamer
      • Direct Ingestion
      • Mediated Ingestion
    • Camel data streamer
    • Flume streamer
    • Storm data streamer
    • Conclusion
    • What’s next
  • Chapter seven: Distributed computing
    • Compute grid
      • Distributed Closures
      • MapReduce and Fork-join
      • Per-Node share state
      • Distributed task session
      • Fault tolerance & checkpointing
      • Collocation of compute and data
      • Job scheduling
    • Service Grid
      • Developing services
      • Cluster singleton
      • Service management & configuration
    • Developing microservices in Ignite
Labels:

Comments

Post a Comment

Popular posts from this blog

8 things every developer should know about the Apache Ignite caching

Any technology, no matter how advanced it is, will not be able to solve your problems if you implement it improperly. Caching, precisely when it comes to the use of a distributed caching, can only accelerate your application with the proper use and configurations of it. From this point of view, Apache Ignite is no different, and there are a few steps to consider before using it in the production environment. In this article, we describe various technics that can help you to plan and adequately use of Apache Ignite as cutting-edge caching technology. Do proper capacity planning before using Ignite cluster. Do paperwork for understanding the size of the cache, number of CPUs or how many JVMs will be required. Let’s assume that you are using Hibernate as an ORM in 10 application servers and wish to use Ignite as an L2 cache. Calculate the total memory usages and the number of Ignite nodes you have to need for maintaining your SLA. An incorrect number of the Ignite nodes can become a b...
Post a Comment
Read more

Analyse with ANT - a sonar way

After the Javaone conference in Moscow, i have found some free hours to play with Sonar . Here is a quick steps to start analyzing with ANT projects. Sonar provides Analyze with ANT document to play around with ANT, i have just modify some parts. Here is it. 1) Download the Sonar Ant Task and put it in your ${ANT_HOME}/lib directory 2) Modify your ANT build.xml as follows: <?xml version = '1.0' encoding = 'windows-1251'?> <project name="abc" default="build" basedir="."> <!-- Define the Sonar task if this hasn't been done in a common script --> <taskdef uri="antlib:org.sonar.ant" resource="org/sonar/ant/antlib.xml"> <classpath path="E:\java\ant\1.8\apache-ant-1.8.0\lib" /> </taskdef> <!-- Out-of-the-box those parameters are optional --> <property name="sonar.jdbc.url" value="jdbc:oracle:thin:@xyz/sirius.xyz" /> <property na...
Post a Comment
Read more

Quick start with In memory Data Grid, Apache Ignite

UP1: For complete quick start guide, see also the sample chapter of the book "High performance in-memory computing with Apache Ignite" here . Even you can find the sample examples from the GitHub repository . IMDG or In memory data grid is not an in-memory relational database, an NoSQL database or a relational database. It is a different breed of software datastore. The data model is distributed across many servers in a single location or across multiple locations. This distribution is known as a data fabric. This distributed model is known as a ‘shared nothing’ architecture. IMDG has following characteristics: All servers can be active in each site. All data is stored in the RAM of the servers. Servers can be added or removed non-disruptively, to increase the amount of RAM available. The data model is non-relational and is object-based.  Distributed applications written on the platform independent language. The data fabric is resilient, allowing non-disruptive au...
Post a Comment
Read more