It used to be that the only way to improve application performance was to add a cache. But caches like Redis don't understand SQL. They require you to modify your applications with non-SQL coding and data models, and copy and synch data across two different models. They don't support ACID transactions very well. And they have their limits when it comes to scalability.
Then came in-memory computing platforms and Apache® Ignite™. Apache Ignite not only preserves SQL by sliding in-between applications and databases as an In-Memory Data Grid with out-of-the-box RDBMS support, native SQL (ODBC/JDBC) and ACID transaction support. It supports most transactional and analytical in-memory needs, including high volume, low latency, petabyte-scale data storage and processing for applications, and streaming.
Learn why HomeAway® and others are choosing Apache Ignite and the enterprise-ready version of Apache Ignite from GridGain® to handle their in-memory computing needs, and moving away from traditional caches like Redis. This session will explain how:
- In-memory technologies have evolved from caches to in-memory computing platform
- Apache Ignite slides in-between existing applications and SQL databases to improve performance and scale
- Apache Ignite native SQL and ACID transaction support works
- Apache Ignite in-memory storage and collocated computing scales out linearly to avoid scale limitations with traditional caches
VP, Developer Relations in R&D at GridGain; Apache Ignite committer and PMC member