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)

Exploring the Data Grid

Apache Ignite data grids adhere to the JCache specification JSR 107. The JSR 107 specification defines five core interfaces to work with caches:

  • CachingProvider: Defines the API to create, manage and configure CacheManagers
  • CacheManager: Defines APIs to create, manage and configure Caches
  • Cache: Stores key-value pairs
  • Entry: Single key-value pair stored in a cache
  • ExpiryPolicy: Each cache Entry has a time to live. During this time, you can access, update, or remove the entry, but after that, the entry expires. The ExpiryPolicy defines when an Entry will expire.

The JCache API defines the following interfaces to customize cache operations: EntryProcessor, CacheEntryListener, CacheLoader, and CacheWriter.

Let's create a cache and store objects in a data grid.

Create a Java class, Key, as a key to a cache and Pojo as a value:

class Key implements...