A brief thought on last week's release of Oracle Database 12.1. Bingo. Strike right down the heart of the plate. Goal. Everything I hoped it would be. And the multi-tenant add-on is the killer feature. The concept of single data-base containers for multiple pluggable databases makes the concept of manage-many-as-one a huge cost savings.
Multi-tenant makes the economies of scale from SaaS a reality in the Oracle world. Big pickup for Oracle as they continue to execute on their "all cloud all the time" strategy. Huge pickup for Oracle database and apps customers with multiple instances (TEST, QA, PROD), whether on cloud or on premise - set things up once, have system-wide metadata, then pluggable databases. Even more: think about the possibilities with the recently-announced Oracle-Salesforce partnership.
In the past, I've written about the complexity of the infrastructure behind Fusion Applications. I'm a fan, but all the moving parts have worried me. 12.1 reduces this concern for me by orders of magnitude. One container for system metadata with pluggable databases. Build provisioning data and parameters once, use many times…which leads to consistency between database environments. Seriously cool stuff.
Even cooler…you'll get the same type of value with 12.1 multi-tenancy with the Applications Unlimited products. Because it's done at the database level rather than at the application tier, manage-many-as-one flows across all the Oracle Applications product families.
OK, I'm blathering. Rather than continue my de-evolution into a full-bore. babbling fan-boy, check out what you need to know here. Then sit back for a moment and think creatively about the possibilities. Apps, Exadata, private and public cloud…the head spins a bit, doesn't it?
Folks, as I see it, this is big. Oracle has put skin into the multitenancy game in a big way, and with a very creative approach. How do you see it? Find the comments.