Chapter 1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode
Memory Is the New Disk
Prior to 2002, memory was considered expensive and disks were considered cheap. Networks were slow(er). We stored things we needed access to on disk and we stored historical information on tape.
Since then, continual advances in hardware and networking and a huge reduction in the price of RAM has given rise to memory clusters. At around the same time of this fall in memory prices, GemFire was invented, making it possible to use memory as we previously used disk. It also allowed us to use Atomic, Consistent, Isolated, and Durable (ACID) transactions in memory just like in a database. This made it possible for us to use memory as the system of record and not just as a “side cache,” increasing reliability.
What Is Pivotal GemFire?
Is it a database? Is it a cache? The answer is “yes” to both of those questions, but it is much more than that. GemFire is a combined data and compute grid with distributed database capabilities, highly available parallel message queues, continuous availability, and an event-driven architecture that is linearly scalable with a super-efficient data serialization protocol. Today, we call this combination of features an in-memory data grid (IMDG).
Memory access is orders of magnitude faster than the disk-based access that was traditionally used for data stores. The GemFire IMDG can be scaled dynamically, with ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access