How We Used GridGain to Build a Telephony API System
summary
A Java team at Dino Systems built a fault-tolerant telephony API that must not lose calls when a server fails, and they used Apache Ignite (GridGain) as an in-memory distributed data grid to achieve that. The talk explains concrete in-memory grid features—entry processors, continuous queries, events, SQL queries—and demonstrates practical pitfalls and iterative Java coding exercises showing how to correctly use these features in a distributed system.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:49In-memory grid
- 9:29Counting participants
- 17:25Distributed system issues
- 27:50Conference setup
- 31:44Participant sync
- 43:57Timer task
- 56:13Summary
- 58:37Q&A
related talks
47mHunting issues in a Java app with 31G heap and 500G off-heap: an Apache Ignite case study
45mHow to write fast in Apache Ignite
46mMaintenance #HowInSber: Java DBMS in Critical Systems
32mJava's Ignored Potential: Supercharge Database Apps with Java In-Memory Process
59mApache Ignite Persistence
27mEngineering Scalable AI with Java
01h 25mGetting started with Spring Data and Distributed Database Grids
39mUnlocking Data-Intensive Applications with Virtual Threads