Develop Domain-Driven based Backends with EclipseStore
summary
A small hotel-booking backend uses EclipseStore to persist the live Java object graph as a file-backed, in-process store; the demo shows domain entities (Hotel, Room, Booking, Guest, Price) saved by adding to the root object and calling the store adapter, tests run in ~600 ms, simple REST calls return in 7–70 ms, creating 1,000 guests consumes roughly 1 GB RAM and startup after reload takes ~13 s, so it works and is very fast but memory intensive and favors Java object-graph persistence.
AI-written summary · about
chapters (12)
- 0:00Introduction and welcome
- 1:29Best car and best database
- 8:35Domain-driven design principles
- 14:12EclipseStore overview
- 17:20Demo application setup
- 19:30Domain model implementation
- 27:41Bounded contexts and adapters
- 33:17EclipseStore repository setup
- 35:49Booking service workflow
- 39:44Testing with EclipseStore
- 42:51Live demo and performance
- 46:45Summary and key takeaways
related talks
52mSimplify Persistence: Exploring Spring-Data-Eclipse-Store for Spring apps
55mDatabaseless High-Performance Persistence with EclipseStore...
52mGet Started Coding with EclipseStore...
47mDesigning Great Java In-Memory Object Models
53mJava In-Memory Database-Apps with EclipseStore
53mDatabaseless Data Processing - High-Performance for Cloud-Native Apps and AI
43mEclipseStore - Ultra-Fast Java Cloud-Native Persistence for Microservices and Serverless
22mEclipseStore – The new, ultra-fast Java persistence for the cloud