Ok java bros, is this shit really the means of avoiding SQL ORM persistence once and for all?I've messed with it and seeing some less than consistent/predictable behaviour at times
>>106470401>EclipseStore>EclipseStore is a databaseless Java-native persistence layer for persisting Java objects without object-relational mappings. EclipseStore is the only data storage layer that uses the native Java object model instead of database-specific data structures or formats. It enables storing any Java object graph of any size and complexity ACID-transaction-safe, seamlessly into any binary data storage such as local disk, persistent volumes or cloud object storage such as AWS S3. Micro snapshots of changes to the object graph are regularly saved to the storage. The ACID transaction journal guarantees full consistency. Each snapshot is stored as a bytecode representation of your Java objects appended to the storage using the Eclipse Serializer's highly optimized byte format. Objects are retrieved from the storage and restored in memory, fully automated by just accessing objects in your object graph by calling getters. Lazy-Loading enables running EclipseStore also with low memory cpacity even lower than 1 GB. At system start, only object IDs are loaded into RAM. Related object references (subgraphs) are loaded into memory on-demand only. EclipseStore's philosophy and goal is to extend Java with an ultra-lightweight databaseless Java-native persistence. Using EclipseStore is amazingly easy and convenient and requires only Java knowledge.Hmmmm, this seems interesting.
>>106470498Agreed. I was hoping it'd be a silver bullet. But some of the default behavior is fuct.For example, calling "store" on some of my objects won't walk all the subobjects of members in the reference graph unless I "store" each of them individually, breaking encapsulation :-(Fucking fuct.
