Fresh off the heels of my meandering thoughts on Exadata. I now bring you my thoughts on the future state of database development.
In a word, it's gonna suck.
Just as more memory, faster CPUs and the other hardware improvements over the years...actually, that's what Exadata is. Let me try that again.
You think most database development sucks now, just wait until Exadata becomes commonplace. Why worry about design or good coding practices when you have brute force?
In a private conversation the other day, I compared it to the effect Windows has had on the populace (myself included), making us computer dumb. It's not always a bad thing; as the computer revolution wouldn't be where it is today without Windows because it gave idiots like me a low barrier to entry.
I see more frustration in my future, not less because of Exadata. Toad will reign supreme as hordes of developers write horrible queries...and get away with it.
I see less emphasis on the fundamentals if using THE Database Machine.
I said it above...brute force.
Why bother tuning up front when you have something that powerful?
Why bother tweaking the design when you have something that powerful?
Just drop it in and run. Exadata will cope just fine.
Thankfully, this won't happen soon, because the cost of Exadata is (perceived to be) so high. I will argue that in another rant I'm sure.
As the volume of data grows, there will be a point at which you must start to tune and contemplate a good design.
Just like Windows though, the bar will be lower. That scares me. I've had plenty of problems over the past couple of years, professionally speaking. Plenty of arguments. When oraclue was my DBA, you could get away with murder, because he could figure out a way to tune bad statement n.
Looking at the bright side, my future will full of excitement. I'll just have new things to bitch about.