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)

Deploying microservices on Ignite

Before we proceed with the deployment, we must ask the question: what are microservices?

Microservices is a pattern or style to decompose a monolithic application into multiple loosely coupled services. Each service has a business responsibility, focuses on solving a business domain problem, is independently deployable, and communicates with other services in order to delegate work.

The microservices pattern evolved to solve the following problems with the monoliths:

  • Monolithic apps are not easy to refactor, changes are not local, and they are very tightly coupled.
  • Understanding the application is difficult. Adding a new feature requires cascading changes.
  • Deploying multiple instances requires resources, such as RAM and CPU, and so you need more hardware to spin off multiple instances of your monolithic app.
  • Adopting new technologies, frameworks...