Skip to main content

Larry goes eXtreme!

Two years after the moment that Oracle went into Operating Systems - Unbreakable Linux - today Larry announced that Oracle (partnering with HP) will sell hardware also. And it's not a simple commodity server... It's the HP Oracle Database Machine. This beast contains 8 database servers (with 64 cores in total) and 14 eXadata servers (with 112 cores). And an enormous amount of storage: 1400 times more than the largest iPod! I think it could contain all mp3's in the world...
An eXadata Server (officially known as the HP Oracle Exadata Programmable Storage Server) contains 2 processors with 8 cores each, 12 disks, Enterprise Linux and - and this is the coolest part - Parallel Query processing capability for every disk. By bringing processing capability close to the storage, the amount of data going through the wires from a storage server to a database server is dramatically reduced - because results are passed instead of datablocks. Because of this architecure the performance will remain the same as the database is growing - just add some more servers and it will be fine. So this is the last piece of the grid-puzzle: Next to Fusion Middleware grid and Database Grid, Oracle can provide us now with Storage Grid.
The performance of this thing is gigantic: tests proved that queries will run 10 to 50 (!) times faster than on current available hardware.
And now ofcourse the closing question: What does it cost?
A Database Machine costs $650,000 - which is $4,000 per terabyte, and that is much cheaper than other storage around. Apart from that there is 'some' license involved for the software : $1,680,000 (and surely an annual fee of 15% of that amount). So it's not for free...but it can replace a room full of yout current hardware!
Post a Comment

Popular posts from this blog

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid. The use case I'll cover right here is probably more common - and therefore more useful!

Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user.The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even worse) while you…

Dockerize your APEX development environment

Nowadays Docker is everywhere. It is one of the main components of Continuous Integration / Continuous Development environments. That alone indicates Docker has to be seen more as a Software Delivery Platform than as a replacement of a virtual machine.

However ...

If you are running an Oracle database using Docker on your local machine to develop some APEX application, you will probably not move that container is a whole to test and production environments. Because in that case you would not only deliver a new APEX application to the production environment - which is a good thing - but also overwrite the data in production with the data from your development environment. And that won't make your users very excited.
So in this set up you will be using Docker as a replacement of a Virtual Machine and not as a Delivery Platform.
And that's exactly the way Martin is using it as he described in this recent blog post. It is an ideal way to get up and running with an Oracle database …

Using multiple Authentication Schemes for your APEX application

Recently someone asked me how he could implement multiple authentication schemes for his APEX application. He would like to use (some kind of) Single Sign-on authentication and - as an alternative - an Application Express Authentication. The problem is ... you can only define one Authentication Scheme being "Current" for an application! So how can we solve this issue?

First, we need te be aware that multiple applications can share their authentication by using the same cookie. Thus if you specify "MYCOOKIE" as the Cookie Name in Application A as well as in Application B, you can switch from A to B and back without the need of logging in again. It doesn't matter what Authentication Scheme Type you are using!

Knowing this, we are halfway our solution. We need two Applications. One - the "real" application - using the Application Express Authentication, let's name this one "LAUNCHPAD". And another one using the Single Sign-on Authentication…