Distributed applications using Hazelcast
summary
Explains how Hazelcast turns a JVM heap into an in‑memory datagrid, demonstrates a tiny web app that starts multiple Hazelcast instances with one line, writes and reads a distributed map across nodes, and shows autoscaling and failure behavior: distributed map partitioning moves partitions across members, backup-count behavior creates primaries and backups so reads survive node crashes. Covers executor service, data aggregation across members, monitoring with Management Center, licensing tradeoffs (OSS vs Enterprise) and practical performance and GC caveats.
AI-written summary · about
chapters (10)
- 0:00Introduction to Hazelcast
- 3:31Top features of Hazelcast
- 13:06Hazelcast vs other solutions
- 29:27Hazelcast In-Memory Data Grid
- 33:51Distributed data with Hazelcast
- 42:13Hazelcast Executor Service
- 45:05Hazelcast transactions
- 48:18Hazelcast monitoring and security
- 51:03Hazelcast in production
- 55:07Q&A and closing remarks
related talks
30mDistributed Computing with Hazelcast
55mHazelcast - Hitchhiker’s Guide. Grzegorz Piwowarek. Java Fest 2020 Online
41mWhat can go wrong with the distributed system - the Hazelcast exp...
38mHazelcast That Could: Getting Lightning-Fast Responses at Hundreds of RPS
01h 23mBuilding Highly-Scalable Spring Applications with In-Memory, Distributed Data Grids
41mDistributed Java DBs Under the Hood: Main Components and Interactions Between Them
46mWhat can go wrong in a distributed system - experience from...
47mjava.util.concurrent for Distributed Coordination
