Re: ACIDity of Prevayler 2.6

Klaus Wuestefeld <[email protected]> Wed, 14 Nov 2012 17:05:42 -0200
Newsgroups gmane.comp.java.prevayler
Message-ID <CAMAooZEZbfjykDz=Lz0RjFmNW7MxeTZYZJskiZLy59pwGh7VKQ@mail.gmail.com>
Atomicity is not about detecting human errors in the coding that leads
to the operations in a transaction. It is about cleanly surviving
system crashes.

I would agree Prevayler provides less *Consistency* built in now, not
lack of Atomicity. Consistency, yes, is something that makes sense
from the point of view of a human being.

Even your best RDBMS with your typical constraints will not detect all
possible buggy SQL(DML) statements sent to it. That doesnt invalidate
its atomicity.

With the food taster we were consistent with regard to Java's strong
typing + RTEs. Now we are consistent only with regard to Java's strong
typing (which is already better than RDBMS constraints IMHO).

It was a conscious trade-off to become less consistent, on the one
hand, but faster, more newb-friendly, simpler and use half the RAM, on
the other.

It seems to be trivial to implement a Transaction base class that does
food tasting internally, orthogonal to Prevayler, if one so wishes.

Klaus

------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion
_______________________________________________
"Databases in Memoriam" -- http://www.prevayler.org