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

Benchmarking high performance java collection framework

I am an ultimate fan of java high performance framework or library. Java native collection framework always works with primitive wrapper class such as Integer, Float e.t.c. Boxing and unboxing of wrapper class to primitive data type always decrease the java execution performance. Most of us, always looking for such a library or framework to works with primitive data type in collections for increasing performance of Java application. Most of the time i uses javolution framework to get better performance, however, this holiday i have read about a few new java collections frameworks and decided to do some homework benchmarking to find out, how much they could better than Java native collection framework. I have examine two new java collection framework, one of them are fastutil and another one are HPPC. For benchmarking i have used java JMH with mode Throughput. For benchmarking i took similar collection for java ArrayList, HashSet and HasMap from two above described frameworks. Col...
Post a Comment
Read more

Apache Ignite Baseline Topology by Examples

Ignite Baseline Topology or BLT represents a set of server nodes in the cluster that persists data on disk. Where, N1-2 and N5 server nodes are the member of the Ignite clusters with native persistence which enable data to persist on disk. N3-4 and N6 server nodes are the member of the Ignite cluster but not a part of the baseline topology. The nodes from the baseline topology are a regular server node, that store's data in memory and on the disk, and also participates in computing tasks. Ignite clusters can have different nodes that are not a part of the baseline topology such as: Server nodes that are not used Ignite native persistence to persist data on disk. Usually, they store data in memory or persists data to a 3rd party database or NoSQL. In the above equitation, node N3 or N4 might be one of them. Client nodes that are not stored shared data. To better understand the baseline topology concept, let’s start at the beginning and try to understand its goal and what ...
Post a Comment
Read more