Distributed Caching For Your Next Node.js Project
summary
Demonstrates Hazelcast as a distributed in‑memory cache for Node.js with an Express microservice that caches GitHub org data, using the Hazelcast Node.js client and a Pivotal Cloud Foundry tile on AWS. Shows a 3‑node cluster scaled to 4 nodes live, stores repo lists in a multi map, uses a near-cache in the Node process, measures uncached calls ~500 ms vs cached ~100 ms, and uses entry processors and listeners for server‑side updates — demo runs and scales without losing data.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker intro
- 1:05Why use caching in apps
- 3:13Distributed cache benefits
- 7:08Data distribution patterns
- 10:19Hazelcast overview
- 13:10Demo setup and Node.js app
- 17:50Cache hit demonstration
- 20:04Near cache and listeners
- 22:15Performance comparison
- 23:41Hazelcast features
- 25:30Scaling the cluster
- 27:05Node synchronization
- 30:20Q&A session
related talks
46mCaching Made Bootiful
43mWhere Is My Cache? Architectural Patterns for Caching ...
47mCaching beyond simple put and gets
46mEdge Performance with In memory NoSQL
42m3 easy performance improvements in your microservices architecture
01h 58mBeyond the Cache with Redis + Node.js
40mLiving on the Edge
46mA Hitchhiker’s Guide to Caching Patterns