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)

Processing transactions

Apache Ignite supports atomic and ACID-compliant transactional cache operations. In ACID-compliant mode, you can perform more than one cache operation (same key, different key, different cache) together. Either all of these operations will be committed or none of them will be; there won't be any partial execution of operations.

Suppose you want to update two values:

   cache.put(2, value1);
cache.put(3, value2);

If the preceding two operations are wrapped inside a transaction and the second update fails, then the first update will be rolled back.

Ignite supports two modes for cache operations: atomic and transactional. In atomic mode, each cache operation is committed individually. For example, if cache.put(3, value2) fails, the first update, cache.put(2, value1), will still be committed.

Atomic mode performs better than transactional mode because...