My adventure in learning CPI: Part 2 | Deployment Models
This blog post is a part of a series of blog posts related to SAP Cloud Platform Integration. The previous blog is:
- My adventure in learning CPI || Part 1 || All about SAP Cloud
Welcome to the 2nd Part of my Cloud Journey.
The first topic which I want to cover is the Deployment Model. A deployment model defines how a company deploys software, which could be onPremise, in the Private Cloud or Public Cloud. It basically describes various possible approaches when it comes to deployment in terms of infrastructure, software, hardware, licensing, and software development lifecycle management.
Types of Deployment Model:
- Hybris Cloud
- Managed Cloud
- Private Cloud
- Public Cloud
These models can be differentiated using the following characteristics:
- Exclusiveness (single vs. multiple customers)
- Access type (VPN vs. web access only)
- Location of the hardware (customer, 3rd party or cloud provider)
- Infrastructure and application management provider (customer, 3rd party or cloud provider)
- Upgrade flexibility/ automation (prescribed by customer or cloud provider)
- Possibility for modifications
- Type of configuration (standardized, guided or full access)
- Pricing model (perpetual vs. subscription-based)
Now let us understand the Deployment Models in details.
1. Hybrid Cloud: As the name suggests, this deployment model comprises of a mix of two or more distinct deployment models (typically onPremise or private or public cloud deployments). By joining the dedicated and cloud resources, businesses can establish an IT landscape that provides the best balance of convenience and security for the company.
2. Managed Cloud (HEC): The managed cloud is usually built on a private cloud platform with dedicated hardware owned by the cloud provider, although certain non-location specific cloud services can be adapted to the requirement of the customer.
This approach allows companies to tap the power of cloud computing without the pain of becoming expert in everything. In the SAP context, the private managed cloud offering is the SAP HANA Enterprise Cloud.
3. onPremise: The software is deployed on servers at the Customer’s premises, where the customer manages and controls the infrastructure, software and data.
This is a classic approach, with no usage of cloud.
4. Private Cloud: This implies resources dedicated exclusively to one specific customer, while infrastructure is owned, managed, operated by the customer or a third-party, and it located on the premises of the customer or a third party.
5. Public Cloud: The resources are located on the cloud provider’s premises, and are shared by multiple customers accessing them via the internet.
Since, it is a shared once hence, it is not that flexible when it comes to customization, downtime or maintenance window.
What about SAP Cloud Platform ?
Service Model: PaaS (Platform as a Service)
Deployment Model: Public Deployment Model
That’s it for now. Shall continue in the next blog.
Thanks for the read.
SAP C4C and CPI Consultant.