Continuing Prevalence "Brief run-down on two significant paradigms that have been becoming a lot more visible, presumably because they're good at...". As long as you define "it" in the strictest sense of what you're doing. If it's anything like persistently storing data (not objects, data) then Prevalyer isn't it. That being said, it's a finalist in the Jolt Awards.
Here's a bunch of links:
* Prevayling Stupidity,
* The Prevayler,
* Object Prevalence: Get Rid of Your Database?, and
* The first message on the AJUG maling list on Prevalyer. It includes replies like, "Prevayler serializes incoming transactions but not the result of executing each transaction. You don't have change (before or after) images. Undoing a failing transaction cannot be accomplished."
Revisiting the DBDebunk web site:
* MORE ON THE STATE OF THE INDUSTRY AND SQL.
* To O OR to R: IS THIS A DATABASE QUESTION?.
We've been considering adding to iTQL the MAYBE operator, to reduce the complexity of writing joins when querying RDF data (more on the MAYBE operator by Date).