Introduction to EclipseStore Coding
summary
EclipseStore runs inside the JVM and persists actual Java object graphs with automatic numeric object IDs and lazy loading via a concrete Lazy<T> type; start a manager with embeddedStorage.start and use store or storeAll (the latter is an atomic all-or-nothing commit). Cold subgraphs are evicted by a Lazy reference manager. Custom type handlers can compact binary layout — the example shows a 60–70% binary shrink — and a CLI migrator converts MicroStream projects; backups can target S3.
AI-written summary · about
chapters (20)
- 0:00Welcome and introduction
- 1:50EclipseStore overview and migration
- 2:57Problems with traditional persistence
- 4:45EclipseStore solution and benefits
- 7:44Architecture and simplicity
- 8:52Basic setup and configuration
- 10:17Root object and lazy loading
- 13:46Configuration options
- 14:07Loading data approach
- 16:16Lazy loading in practice
- 21:23Lazy reference management
- 24:01Storing data and transactions
- 27:33Eager storing configuration
- 29:04Transient fields and deletion
- 32:14CRUD operations summary
- 32:36Custom type handlers
- 38:16Type mapping for versioning
- 41:08Backup and housekeeping
- 42:57Migration from MicroStream
- 46:13Q&A session
related talks
22mEclipseStore – The new, ultra-fast Java persistence for the cloud
43mEclipseStore - Ultra-Fast Java Cloud-Native Persistence for Microservices and Serverless
52mGet Started Coding with EclipseStore...
57mJava In-Memory Database-Apps with EclipseStore
55mDatabaseless High-Performance Persistence with EclipseStore...
53mDatabaseless Data Processing - High-Performance for Cloud-Native Apps and AI
44mCaching Unleashed: Revolutionizing Java Performance
52mSimplify Persistence: Exploring Spring-Data-Eclipse-Store for Spring apps