Drivers of hybrid cloud and multicloud setups
Hybrid and multi-cloud setups can be temporary and only maintained for a limited time to facilitate migration. However, these settings are also likely to represent the future state of most organizations as they build new systems and evolve existing systems to make each system perform at its best, no matter where the system is set up. As a result, hybrid cloud and multicloud setups can become permanent fixtures in IT environments.
A hybrid or cloud database setup may not be an end in itself, but a means to meet business needs. Therefore, it is important to understand these requirements before choosing the right hybrid cloud or multi-cloud setup.
Business Drivers and Constraints
Common drivers and constraints on the business side include:
Reduce capital expenditures or general IT spending.
Increase flexibility and agility to better respond to changing market demands.
Build capabilities that might be difficult to implement in existing environments, such as advanced analytics services.
Improve service quality and availability.
Increase transparency of costs and resource usage.
Comply with laws and regulations governing data sovereignty.
Avoid or reduce vendor lock-in.
Design and Development Drivers
Common drivers for design and development include:
Automate and accelerate application releases for faster time to market and shorter cycle times.
Take advantage of advanced APIs and services to accelerate development.
Accelerates provisioning of computing and storage resources.
Operating Requirements and Limitations
Operating considerations and limitations include the following:
Ensure consistency of authentication, authorization, auditing, and policies across computing environments.
Reduce complexity with consistent tools and processes.
Provides visibility across environments.
Architectural limitations
Architecturally, the biggest constraints typically come from existing systems and may include the following:
Dependencies between applications.
Performance and latency requirements for communication between systems.
Rely on hardware or operating systems that may not be available in the public cloud.
Licensing Restrictions.
Overall objective:
The goal of a hybrid and multicloud strategy is to meet these requirements through a plan that describes:
Which workloads should be run or migrated in each computing environment.
Which patterns are suitable for various workloads.
Which technology and network topology to use.
Hybrid and multi-cloud setups can be temporary and only maintained for a limited time to facilitate migration. However, these settings are also likely to represent the future state of most organizations as they build new systems and evolve existing systems to make each system perform at its best, no matter where the system is set up. As a result, hybrid cloud and multicloud setups can become permanent fixtures in IT environments.
A hybrid or cloud database setup may not be an end in itself, but a means to meet business needs. Therefore, it is important to understand these requirements before choosing the right hybrid cloud or multi-cloud setup.
Business Drivers and Constraints
Common drivers and constraints on the business side include:
Reduce capital expenditures or general IT spending.
Increase flexibility and agility to better respond to changing market demands.
Build capabilities that might be difficult to implement in existing environments, such as advanced analytics services.
Improve service quality and availability.
Increase transparency of costs and resource usage.
Comply with laws and regulations governing data sovereignty.
Avoid or reduce vendor lock-in.
Design and Development Drivers
Common drivers for design and development include:
Automate and accelerate application releases for faster time to market and shorter cycle times.
Take advantage of advanced APIs and services to accelerate development.
Accelerates provisioning of computing and storage resources.
Operating Requirements and Limitations
Operating considerations and limitations include the following:
Ensure consistency of authentication, authorization, auditing, and policies across computing environments.
Reduce complexity with consistent tools and processes.
Provides visibility across environments.
Architectural limitations
Architecturally, the biggest constraints typically come from existing systems and may include the following:
Dependencies between applications.
Performance and latency requirements for communication between systems.
Rely on hardware or operating systems that may not be available in the public cloud.
Licensing Restrictions.
Overall objective:
The goal of a hybrid and multicloud strategy is to meet these requirements through a plan that describes:
Which workloads should be run or migrated in each computing environment.
Which patterns are suitable for various workloads.
Which technology and network topology to use.