Lots of noise (and some gems) about the acquisition of Sun by Oracle on Twitter today. But contrary to Oracle's content servers, Twitter seems to be holding up quite well.

I half-jokingly added my own noise saying that now's a good time for people worried about MySQL's future to switch to JCR, and Bergie agrees!

Rereading this post, what follows sounds a bit like marketingspeak, but it's not - just enthusiasm!

We've been discussing the similarities between Midgard and JCR earlier this year with him and also with Jukka, and it's amazing to see how close the models of Midgard and JCR are. With their TYPO3CR, Typo3 also agree that the JCR model is extremely well suited for content storage and manipulation. Midgard2 doesn't use the JCR APIs, but as mentioned above the concepts are very similar.

Having made the move myself from wire-some-object-relational-stuff-on-top-of-sql-and-suffer-forever to JCR as an API that's designed from the ground up to work with granular content, including observation, unstructured nodes and many other nice features, I'm not going back!

If you're working with content (and yes, everything is content anyway), and started wondering about the future of MySQL today, now might be a good time to take another look at JCR. Apache Jackrabbit has been making huge progress in the last two years with respect to performance and reliability, and Apache Sling makes it much easier than before to get started with JCR, mostly due to its HTTP/JSON storage and query interface which takes the J out of JCR.

Never had so many (meaningful) replies and retweets on Twitter before today - but I started by wondering why CMIS wants to reinvent WebDAV, so no wonder. We'll save that one for another time I guess.