A growing set of demos for EclipseStore — the high-performance Java object persistence engine (formerly MicroStream). Each demo is paired with an article walking through the design decisions.

Topics covered

  • Basic storage — getting an object graph onto disk in three lines of code
  • Complex data structures — maps of maps, cyclic references, large collections
  • High-performance serialiser — the binary format, throughput benchmarks
  • Migration patterns — schema evolution without classical migrations
  • Threading & transactions — how EclipseStore handles concurrent writers
  • Comparison to JPA/Hibernate — when it’s the right tool, when it isn’t

Why EclipseStore

For a lot of Java apps the database is the boundary — you spend more time mapping objects to rows than doing actual work. EclipseStore inverts that: your object graph IS the database. No mapping, no ORM, no SQL.

It’s not a fit for every use case (try it on transactional reporting at scale and you’ll feel the boundaries quickly) — but for many domain models, the mental simplicity is a huge unlock.

Articles, benchmarks and links to the demo repos live in the EclipseStore category.