Case Study: Provisioning a Multi-Site In-Memory Database
summary
Shows a concrete run book: use Spring GemFire plus a small metadata service and launcher wrappers to auto-register locators and WAN gateways, trigger a server-side rebalance function, and scale cache nodes. Claims drop provisioning from days–weeks to 14 VMs in ~15 minutes by deploying east/west clusters, wiring IPs at runtime, and awaiting quorum before rebalancing. Demonstrates actual artifacts (launchers, spring contexts, rebalancer function) and a live deployment that works end-to-end.
AI-written summary · about
chapters (21)
- 0:00Intro
- 2:51Introductions
- 6:03Deployment
- 7:46What is JimFire
- 14:18Update Code
- 20:43Configuration Overview
- 26:09Topology
- 26:44Sequence Flow
- 30:38Rebalancing
- 33:09Rebalancing code
- 35:47Expected servers
- 38:06Spring Gymfire
- 39:22Manual Configuration
- 40:07Server Configuration
- 41:32Spring JMX
- 42:17Cache Server
- 43:27Shell Problems
- 46:37Rebalancer
- 49:20Runbook
- 50:33GFish
- 54:35Blueprint
related talks
01h 23mBuilding Highly-Scalable Spring Applications with In-Memory, Distributed Data Grids
48mScaling Spring Boot Applications in Real-Time - John Blum, Luke Shannon
38mDeploying Database Clusters in the Cloud
26mMulti-Cloud Native Data with Spring and VMware Data Solutions
46mEdge Performance with In memory NoSQL
28mHybrid database-as-a-service for DevOps
31mReimagining the Future: Where the Market is Evolving
20mHow to Build a High Performance App Using Cloud Foundry and Redis