Sanne Grinovero I agree with you, but it's too easy (ehm, or it should be) to turn the slow -> fast knob by enabling caching without verifying application needs. And I know that DBs don't have serializability as default either. I can't tell what majority of users expect, but as a Java guy I assume JMM unless told otherwise. Don't hide behind the "expert tuning" term - I doubt most of the experts give it second thoughts if it passes couple of simple tests, considering "middleware" devs to handle the trickery.

We've warned users about query cache lag, we should do the same for domain data. We could argue if RC is sufficient and should be chosen as default (probably you're right as many people use 4.x which does not give you much more), but IMO the default should be the connection isolation level. Turning the cache on should not change anything. Steve Ebersole do we want any more knobs in 6.0 (some enum in the o.h.annotations.Cache I guess)? Or do we want 2LC to be just RC-mostly-not-stale? In the latter case, we could get rid of a lot of the complexity that I've introduced.