The GridGain Systems In-Memory Computing Blog

GridGain recently published a micro-learning unit on GridGain University that delves into the different data loading strategies for Apache Ignite. These strategies include initial/regular batch load from files, database loading, real-time streaming, and ETL (Extract Transform & Load). Here is an overview of some of the key strategies. Watch the full 9-minute video here. Initial / Regular…
To improve application and query performance, developers frequently use summary tables. The summary table pattern is where we feed data into an Apache Ignite or GridGain cluster into two tables: the original data; and a summary, or rollup, of that data. With GridGain’s SQL engine, it’s not always necessary to have a summary table! For many, perhaps most, use cases, the fact that the data is…
In-memory computing can provide tremendous benefits for the 5G ecosystem. We’ve seen the marketing for the fifth-generation mobile networks. The benefits of 5G for end-users are easy to understand. Speeds faster than your home broadband and latencies only a little slower promise to be game-changers for consumers, enhancing existing applications and opening open entirely new categories that we…
In-Memory Compute and Data Grids serve as the fundamental components of an in-memory architecture. The objective of In-Memory Data Grids (IMDG) is to ensure exceptionally high data availability by storing it in memory in a highly distributed and parallelized manner. By loading terabytes of data into memory, IMDGs can effectively handle most of the requirements for processing Big Data today.…
MySQL is a popular open-source relational database management system (RDBMS) that has certain limitations when it comes to Big Data analytics. In this context, this post will delve into five key MySQL limitations that can be addressed by taking a modern approach to the data architecture. 1. Delivering Hot Data In large Big Data analytics applications, the data cache stored in RAM can grow very…
Held on June 6, 2023, this year's Ignite Summit showcased the breadth and flexibility that make Apache Ignite a foundational technology for many demanding data use cases. Presenters represented a wide range of organizations, from financial services and telecommunications to programming language development.  Organized by GridGain and the Apache Ignite community, Ignite Summits attract engineers…
Why is it necessary to distribute data?  As systems that require data storage and processing evolve, they often reach a point where either the amount of data exceeds the storage capacity, or the workload surpasses the capabilities of a single server.  In such situations, there are two useful data distribution solutions: data sharding and migrating to a distributed database. Both solutions…
This tutorial walks you through the process of creating a Spring Cloud-based RESTful web service that uses Apache Ignite as a high-performance, in-memory database. The service is a containerized application that uses HashiCorp Consul for service discovery and interacts with an Apache Ignite cluster via Spring Data repository abstraction. For containerization, we use Docker. Apache® Ignite™ is…
Apache Ignite has the ability to scale horizontally, allowing you to handle the data generated by your applications and services. When your Apache Ignite cluster is using excessive memory, you can utilize horizontal scaling, which is one of the fundamental architectural capabilities of Ignite. While the common advice is to "throw more resources into the cluster," it is often not practical or…
There are two significant categories in in-memory computing: In-Memory Database and In-Memory Data Grids. This post aims to present a concise version of thoughts on this topic, with insights gained from a recent analyst call aiding in organizing the information. Nomenclature of In-Memory Database vs In-Memory Data Grid Let's start by clarifying the terminology and buzzwords. The term "In-…