Hybrid Layers
Overview
So far our migration patterns have focused on the applications themselves - looking at how we can move or enhance a single or group of related applications as complete units. The hybrid layers approach is fundamentally different in that it takes a technology-led view of applications. In the earlier discussion of Modernization Patterns we broke down an application into a set of components like this :
When we talk about hybrid layers, we take one of those components across a broad set of applications and move just one layer, leaving all the others in place. A multi-cloud version of this approach is when different components of the application are deployed in different clouds. While this may have been impossible just a few years ago, the improved networking between on-premises and public cloud, and between different public clouds has enabled this as a practical option.
For Oracle, we focus on our strength, which is database, and we often see customers moving just their database estate to OCI, or also moving their database estate to Oracle and their application servers to a competing cloud.
Use
The most common use, by far, of this approach is to deliver Database-as-a-service (DBaaS). While compute services are not highly-differentiated across different clouds, database services remain highly differentiated - especially with Oracle Database and Exadata - with the result that customers often choose to put their Oracle databases on OCI.
Use Cases
- Database-as-a-service