Prevayler: ACID persistence for plain old Java objects (2013)
1–10 of 14 posts
Re: Prevayler: ACID persistence for plain old Java objects (2013)
#2Re: Prevayler: ACID persistence for plain old Java objects (2013)
#3Re: Prevayler: ACID persistence for plain old Java objects (2013)
#4Re: Prevayler: ACID persistence for plain old Java objects (2013)
#5Re: Prevayler: ACID persistence for plain old Java objects (2013)
#6If one does need Java object persistence perhaps this seems better maintained [1]
Re: Prevayler: ACID persistence for plain old Java objects (2013)
#7Re: Prevayler: ACID persistence for plain old Java objects (2013)
#8Quite nice for rapid development without getting buried by ORMs or NoSQL, and it becomes easy to migrate the "soft" JSONB columns to "hard" DDL schemas as performance requires it.
Re: Prevayler: ACID persistence for plain old Java objects (2013)
#9Maybe not the best time to promote a library using Java serialization. Java Serialization is probably the number 1 source of serious Java vulnerabilities since applets, and it isn’t even particularly fast compared to other serialization libraries that target JSON or something else
Re: Prevayler: ACID persistence for plain old Java objects (2013)
#10I recently implemented something like this in Go, basically just a tiny bit of glue between encoding/json and pgx (for JSONB columns). With generics, it's trivial to wrap any Go struct into an ACID record. Quite nice for rapid development without getting buried by ORMs or NoSQL, and it becomes easy to migrate the "soft" JSONB columns to "hard" DDL schemas as performance requires it.
Are there cases wherein GIN indexes on the JSONB columns aren't sufficient for performance requirements?