Over time, NoSQL and big data will slow Oracle RDBMS's long-term growth, but it won't deliver a death blow anytime soon -- except, perhaps, to Oracle RAC
Like many people, I cheer any sign of Oracle's downfall and chuckle at the thought of Larry Ellison having some misadventure on the high seas. Who doesn't? But the sad fact is that, despite all the buildup, NoSQL and big data do not threaten Oracle or the RDBMS paradigm in the near term
On the other hand, there's a decent chance NoSQL will take a big bite out of Oracle RAC (Real Application Clusters). Here's why.
Undoubtedly I’ll be trolled by people who will give me Google’s stock price, point out how many billions more it makes than my company or something else as trite. So if you are a Google fanboy, go ahead and skip to the end - no need to read the rest - and begin your flame.
As I write this it will have been exactly 1 year to the day (Oct 12, 2011) since Google engineer Steve Yegge explained what Google is habitually doing wrong. In that
time, I’m afraid little progress has been made.
Tired of dreary disaster scenarios? Then here's a grab bag of topics you shouldn't bother fretting over.
I don't know about you, but I have enough to worry about -- so much, in fact, I sometimes feel it's easier to enumerate the things I don't need to fret over. I find the exercise soothing. No thrills here, just chill:
So it looks like the SAP guys are still at it. Not only did they get Granny deployed on SAP Netweaver with no configuration changes, but now they have:
It seems like another PaaS vendor has gone wild with granny. Yesterday I wrote about how honored we were that SAP deployed granny on their NetWeaver PaaS and today I'm proud to report that Granny can have her ever growing addressbook needs (she was wild in her 20s so she has a lot of grandkids) served by Cumulogic on HP's cloud. While I couldn't get the link they provided to work, they may have taken it down. Here is what they did to make it work:
So one of my old JBoss buddies, Max Rydahl Andersen of Hibernate fame, improved on our process for making Granny's Addressbook deploy on Red Hat's PaaS, OpenShift and told me over on G+. You can find his Granny running here on OpenShift.
The crux of it is that JBoss AS 7 broke compatibility with the Spring Framework whereas JBoss EAP (their pay-for with EULA version of AS) supports Spring more easily. You just use our main branch of Granny from git and then add this in persistence.xml: