Tuning Ignite in Cloud Infrastructure
summary
A team migrated a large, latency-sensitive Java system using Apache Ignite, Kafka and OpenShift into cloud infrastructure and encountered performance regressions. The talk describes the specific performance problems they faced during cloud migration, how to avoid them, and practical advice and recommendations for successfully migrating high-load distributed storage systems like Ignite.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:28Monolithic architecture issues
- 7:51Microservices and cloud solution
- 12:30Apache Ignite for cloud
- 15:18Thick client pros and cons
- 18:56Thin client setup and issues
- 22:28Thick client alternatives
- 24:33Thin client optimization
- 27:06Cloud performance problems
- 31:01Ignite transactions and locks
- 34:34Cluster failures and recovery
- 36:58Configuration tips
- 41:19Summary and microservices transition
- 42:46Q&A
related talks
33mDistributed Database DevOps Dilemmas? Kubernetes to the rescue!
32mDistributed Database DevOps Dilemmas? Kubernetes to the Rescue
49mBeyond the Data Grid: Fast Data Processing with Apache Ignite
47mHunting issues in a Java app with 31G heap and 500G off-heap: an Apache Ignite case study
53mLeveraging Caching For Cloud Native Applications
41mDistributed Java DBs Under the Hood: Main Components and Interactions Between Them
24mMigrations under Production Load: How to Switch...
45mMigrating Mission Critical Workloads from Mainframe to Open...
