Book Image

Apache Ignite Quick Start Guide

By : Sujoy Acharya
Book Image

Apache Ignite Quick Start Guide

By: Sujoy Acharya

Overview of this book

Apache Ignite is a distributed in-memory platform designed to scale and process large volume of data. It can be integrated with microservices as well as monolithic systems, and can be used as a scalable, highly available and performant deployment platform for microservices. This book will teach you to use Apache Ignite for building a high-performance, scalable, highly available system architecture with data integrity. The book takes you through the basics of Apache Ignite and in-memory technologies. You will learn about installation and clustering Ignite nodes, caching topologies, and various caching strategies, such as cache aside, read and write through, and write behind. Next, you will delve into detailed aspects of Ignite’s data grid: web session clustering and querying data. You will learn how to process large volumes of data using compute grid and Ignite’s map-reduce and executor service. You will learn about the memory architecture of Apache Ignite and monitoring memory and caches. You will use Ignite for complex event processing, event streaming, and the time-series predictions of opportunities and threats. Additionally, you will go through off-heap and on-heap caching, swapping, and native and Spring framework integration with Apache Ignite. By the end of this book, you will be confident with all the features of Apache Ignite 2.x that can be used to build a high-performance system architecture.
Table of Contents (9 chapters)

Writing data to a persistent store

Apache Ignite's distributed clustering model and data grids move data closer to the application and help us to achieve high performance by keeping objects in memory. However, we cannot keep the entire dataset in memory because the RAM is volatile in nature. If the entire cluster goes down, we will lose our precious data. Also, keeping the entire application data in memory can affect the system performance.

The optimal design is to keep the subset of data, the most recently used or active data, in memory and the other set (inactive or not so frequently used data) can be stored in a persistent data store. Apache Ignite supports the following two persistence modes:

  • Native disk-based persistence
  • Third-party data store persistence: RDBMS and NoSQL

In this section, we are going to examine the default native persistence, third-party MySQL...