3 easy performance improvements in your microservices architecture
summary
Three concrete fixes: enable Hibernate second-level cache backed by Hazelcast to cut DB hits; add an HTTP-side proxy using JCache/Spring Boot cacheable to cache individual entities (note list projections don’t auto-cache); and enable session replication via Tomcat integration to remove sticky-session fragility. Demos show Hazelcast configured in Spring Boot, warm vs cold-cache hits, async vs sync DB-write tradeoffs, staleness vs freshness choices, and CAP-mode options (AP default, optional CP subsystem) so teams can pick the acceptable consistency/availability trade-off.
AI-written summary · about
chapters (12)
- 0:00Introduction to Microservices
- 1:53Scalability and Architecture
- 3:24Distributed System Challenges
- 6:24Caching Strategies and Trade-offs
- 8:33Implementing In-Memory Grids
- 12:28Hibernate Level 2 Cache Demo
- 17:00JCache and Alternative Caching
- 19:02Manual Caching Demo
- 22:46Session Replication Techniques
- 24:10Demo: Session Management
- 28:20Conclusion and Summary
- 30:04Questions and Answers
related talks
46mCaching Made Bootiful
47mArchitectural Patterns for Caching Microservices
45mWhere is my cache? Architectural patterns for caching microservices by example
53mLeveraging Caching For Cloud Native Applications
47mCaching beyond simple put and gets
43mWhere Is My Cache? Architectural Patterns for Caching ...
45mCaching in Applications Still Matters
46mA Hitchhiker’s Guide to Caching Patterns