Prevayler Quietly Reaches 2.0 Alpha, Bye RDBMS?

ninejaguar asks: "Slashdot did an article on an Open Source product called Prevayler, which could theoretically resolve all the problems associated with OO's rough courtship with Relational databases. Slashdot covered Prevayler when it was still 1.x. Despite fear, doubt, and memory concerns, it has reached 2.0 alpha. Is anyone currently using this non-database solution in production? If so, has it sped development because of the lack of OO-to-RDBMS complexity? Was there a significant learning curve to speak of? The LGPL'd product could be incorporated into proprietary commercial software, and few might know about it. Is anyone considering using it in a transactional environment where speed is the paramount need? And, are there any objections to using Prevayler that haven't been answered at the Prevayler wiki? Would those who use MySQL find Prevayler to be a better solution because it's tiny (less than 100kb), 3000 times faster and is inherently ACID compliant?" Update: 09/24 19:25 GMT by C :Quite a few broken links, now fixed.

"We've used relational databases for years despite incompatibilities in SQL implementation. Accessing them from an OOP paradigm has been so tedious, that Object-Relational mapping technologies have sprouted all over the Open Source landscape. Some competing examples and models are Hibernate, OJB, TJDO, XORM, and Castor; which in turn have supporting frameworks such as Spring and SQLExecutor. Because SQL is the dominant form of interfacing with the data in an RDBMS, there's now a specification to offer it a friendlier OO face.

Most of the above, including the SQL-variants, arguably appear to add yet another layer of complexity (even if only at the integration level) where they should be taking complexity away. These solutions are put together by some very smart people, but it's inescapable to get that feeling someone is missing the forest (simple answer) because all the trees (incompatible models) are in the way. If there are so many after-the-fact solutions attempting to simplify relational database access and manipulation from OO, isn't it reasonable to think that there is something generally wrong with trying to cobble-together two disparate concepts with what are essentially high-caliber hacks? Is Prevayler a better way?"

Comments

Re:Persistance does not make a DB

[angel'o'sphere]

What assholes.
I think the asshole is you.
Either you do not understand what tehy say, or you did not read the article on their site.


That's obviously the stupidest thing ever. How about, "When I don't have the time and money to connect all my company's SQL DB stuff to your java stuff." Obviously my scenario encompasses a whole lot more users than their three, and perhaps explains why no one is using their product.

If you HAVE AN SQL DATABASE, then you wont obviously not use prevayler.
But what if you start writing an application from scratch? No data, no data base, green hills?
Then read theri wiki and you find reasons why you then may find prevayler excellent.

Come on boy! /. makes an articel about a "thing" on a website ... with a wiki.

And you post here: What assholes

I hope the prevayler guys have an education and are more gentlemen like you .... or it might be your face that get smashed when you accidently meet one of them at a software convent.

angel'o'sphere

Re:Huh?

[jonfelder]

I believe "take control of Iraq's oil supply" would be the answer to step 2.

Another possibility would be, "receive kickbacks from the $150 billion+ spent on the war".

Re:Persistance does not make a DB

[MattRog]

But the thing is that the RDBMS (which a 'true' one does not exist, of course) using logic and a sound model ensures that your data is safe and correct. This Prevlayer product has none of these and is basically, "We thought this might be neat, but can't really back it up by any sort of sound foundation. Good luck!"

Re:Please, enough of the hyperbole bullshit

[AntiOrganic]

Especially considering how Michael Moore is one of the most sensationalistic "filmmakers" ever. This is, of course, when he's not flat-out trying to deceive his audience to further his agendas.

This isn't to say that he's wrong, but his attitude is a discredit to his message.

Re:3000 times faster than Mysql?

[slimdave]

Sure it's possible -- all you do is let java programmers design a relational database. Ta Da! Instant pile-of-crap. Would anyone believe Microsoft if they posted "3000x faster than ..." results for one of their products? I think not -- these folks are no different. As soon as they post results of an industry standard benchmark (TPC or whatever), the myth will be nicely punctured.