in Washington DC, USA, Oracle formally announced what it calls the
"Oracle Cloud at Customer" service which, from my understanding, is a
new term for the combination of Oracle hardware running in your data
centre (see Oracle's Public Cloud Machine - initial thoughts and speculation), the Oracle public cloud software running on this hardware, and remote management by Oracle.
Note that, seemingly as of today, the new hardware is called the Oracle Cloud Machine
(it was formerly known as "Oracle Public Cloud Machine" and "Oracle
Private Cloud Machine for PaaS & IaaS"), abbreviated to OCM (no
doubt to the chagrin of Oracle Certified Masters!).
Oracle had its top brass out today, with Thomas Kurian providing the primary keynote:
interestingly Oracle is clearly steering the conversation away from
hardware altogether - there was very little mention of specifications
and nothing about performance (which we usually hear for Engineered
Systems) - this launch was primarily centred on flexibility of service
Firstly let's recap what, in a nutshell, Oracle Cloud (PaaS & IaaS) offers:
- a subscription / pay as you go licensing model,
- simplified provisioning and management using a high degree of automation,
- scalability with the ability to provision and scale up without needing hardware procurement/provisioning,
- standardised, pre-designed architecture and configurations,
- an underlying platform entirely managed & monitored by Oracle.
The Oracle Cloud Machine, in addition to the above, offers:
- low latency to other systems running on your premises,
- a location in your own data centre, behind your own firewall.
Let's look at those two characteristics more closely. With low latency I can see these clear benefits for OCM:
you run applications that interact heavily with existing systems that
will stay on your premises for some time (I'm thinking about mature EBS
or SAP systems, mainframes, large data warehouses) with OCM you will be
able to migrate these applications to Oracle Cloud, such as JCS, more
safely (not dissimilar from carrying out a hardware refresh).
you have applications and databases which you may want to migrate
eventually to Oracle (public) Cloud, but can't (shouldn't) do that all
in one migration, then you could firstly, say, migrate some applications
to OCM and then gradually migrate your databases - thus always keeping
very fast connectivity between the tiers. Once all your environments run
on OCM then it becomes a less challenging/less risky task to migrate
them all to the public cloud should you wish.
If we now think about the benefits from being "in your own data centre, behind your firewall": Read the complete article here.
WebLogic Partner Community
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.
Blog Twitter LinkedIn Forum Wiki