I spent the last 6 month helping customers design, implement and deploy successful Hadoop systems. Over time, you start seeing patterns. Certain things that if the customer gets right before the project event starts increase the probability that the project will finish successfully and on-time.
Lets assume you already took the most important step – you have an actual use-case or a problem to solve, and you think Hadoop could be the right technology to use in this case. What now?
I work for a company that provides betting to consumers in Australia…
In Australia, the three biggest days for betting are typically:
Yesterday was the Caulfield Cup and we breezed through it…always a nice result. Because if we dont we lose lots of money…fast.
But the reason for the blog post is not to gloat (well…not entirely :-)). Its about an important thing about apps under Oracle – here’s my contention:
All that matters is your app.
End of story.
People talk about servers, CPU, flash, disk, bandwidth, memory speed, etc etc etc etc….but all those count for nought if your app is garbage.
To be honest, two years before we deployed our app into production…it was exactly that: garbage.
Three part post
The simple truth is that databases can’t be given to every developer like source code.
Three part post
I’ve spent so many years trying to explain that a “hint” to the Oracle optimizer is an order – if you know how to do it properly – that I finally decided to list the manual references that have made this point over the last 15 or so years. Here’s the list, which ends with a surprising change of flavour. (Emphasis in the body of the text is mine).
As an application designer, you may know information about your data that the optimizer does not know. For example, you may know that a certain index is more selective for certain queries. Based on this information, you may be able to choose a more efficient execution plan than the optimizer. In such a case, use hints to force the optimizer to use the optimal execution plan.
Only a week after Oracle OpenWorld concluded and I already feel like I’m hopelessly behind on posting news and impressions. Behind or not, I have news to share!
The most prominent feature announced at OpenWorld is the “In-Memory Option” for Oracle Database 12c. This option is essentially a new part of the SGA that caches tables in column formats. This is expected to make data warehouse queries significantly faster and more efficient. I would have described the feature in more details, but Jonathan Lewis gave a better overview in this forum discussion, so just go read his post.
Why am I excited about a feature that has nothing to do with Hadoop?