Live data from Hacker News

Prevayler: ACID persistence for plain old Java objects (2013)

prevayler.org

1–10 of 14 posts

Re: Prevayler: ACID persistence for plain old Java objects (2013)

#4
Maybe 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)

#8
I 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.

Re: Prevayler: ACID persistence for plain old Java objects (2013)

#9
post #4

Maybe 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

It works with xstream, and I’m sure it could support Jackson, or whatever. The hard part is picking which layer to serialize and resisting the urge to re-implement Dynamo.

Re: Prevayler: ACID persistence for plain old Java objects (2013)

#10
post #8

I 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.

>migrate the "soft" JSONB columns to "hard" DDL schemas as performance requires

Are there cases wherein GIN indexes on the JSONB columns aren't sufficient for performance requirements?

Post reply on HN