Skip to main content

OOW2011 - Announcing Oracle`s Big Data Appliance

During the Oracle ACE Director briefing, Mark Townsend, VP Database Product Management, did "State of the Union" on the Oracle database. This post is my report of his talk...
At this moment around 55% of the installed base of the Oracle database is on 11.2. Last year, Oracle made more money from selling more database licenses and more options on existing installations.
Mark mentioned that there are customers with 1,000`s of databases (and even one with 80,000!) - all using different versions of the database, of the operating system, storage etc. This situation is very hard to maintain and to keep up and running. Inn Oracle`s view, consolidation into a "private cloud" is the solution, and therefore Oracle offers Exadata. One (or less) databases are easier to secure, easier to make high available and easier to upgrade. And when you use Oracle software troughout your application stack, why not use Oracle hardware as well? So Oracle is striving towards a "red stack" (i.e. all Oracle).

The latest version of the Oracle database is 11.2.0.3. 11.2.0.4 is planned for somewhere next year. After that, Oracle 12 will replace the "g" with a "c" - for "cloud" of course! - and should be available somewhere next year as well. Oracle 12c is not a subject on this OpenWorld. You can sign up for the beta test, which will start in November.
Last week, the Oracle Database Appliance (ODA) was announced. The ODA comes with standard 24 cores, but you can license per core - completely different from the current licensing where you have to pay for all cores that are available in your hardware. In Oracle`s terminology, an "Appliance" is engineered for simplicity, anything called "Exa-whatever" is engineered for speed. Next to the ODA, Oracle announced this Monday the "Big Data Appliance", using a (new) Oracle NoSQL database (based on the Berkeley DB). This appliance will do massively parallel batch processing with Hadoop. Therefore Oracle will distribute Hadoop (and support it as well). There will be an Oracle Data Integrator (ODI) to get the data from Hadoop into a relational Oracle database. Another new product in this appliance is "Oracle R". "R" is open source replacement for SAS - a statistical tool for data-analysts (like the software used by the female computer wizard in the tv-series Criminal Minds). So the BDA consists of this whole stack (as I understood it). The BDA solution (or framework or architecture) is aimed at processing huge bulks of no-SQL data (key-value pairs), like user clicks on website, phone calls etc, but is good for oldfashioned ETL too!

Location:Ellis St,San Francisco,United States

Post a Comment

Popular posts from this blog

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 …

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…

Push changed rows to an Interactive Grid

For pushing changes from the database to the end user, the regular solution is using websockets. A change in a record is detected - using a trigger or using the CQN (Change Query Notification) feature - and a notification is send to a websocket server. That websocket server broadcasts the notification over a channel to all browsers that are tuned in to that websocket channel. Then the browser reacts to that notification, usually showing an alert or refreshing a report. This trick is described on multiple sites, just Google for "oracle apex websockets" or similar.

So back in the old days, we used that notification in the browser to refresh the (interactive) report. But along comes the Interactive Grid (IG). While he full-refresh mechanism still works for IG, an IG has also the option to refresh just one row.  So wouldn't it be awesome that just the changed row(s) get refreshed upon a change in the database, instead of the whole report? Can we do it ... yes we can!
First i…