Exploring Deployment Options

SAP HANA is a database, an appliance, and a platform.

First of all, SAP HANA is a hybrid in-memory database, which combines row-based, column-based, and object-based database technology. SAP HANA can use the parallel processing functions of modern multi-core CPU architectures. SAP applications can use the advantages of current hardware technology, by using this architecture.

Furthermore, SAP HANA is a flexible, data-source-agnostic appliance (an appliance is a combination of hardware and software), which provides the possibility for customers to analyze large amounts of data of SAP and non-SAP systems in real time. The requirement to materialize transformations is therefore no longer necessary. SAP HANA appliance software is a combination of hardware and software, which integrates a number of SAP components, including the SAP HANA database and various data replication systems.

SAP HANA is also an application framework, and a development environment — with the possibility to develop native SAP HANA applications. SAP HANA is the platform for all cloud-based SAP applications, and for the latest SAP product S/4HANA.

The functionality of SAP HANA is as follows:

• Optimized data storage for column-based storage.

• Optimized data compression is, therefore, possible.

• Partitioning and distribution on various processor cores. Shifting of data-intensive calculations, from application to database.

• Processing of geo-specific data/geo-specific data types are supported.

• Text analysis and full text search is supported.

• Successively renewed coding of all SAP applications based on SAP HANA

• Radically simplified data model (redundant tables and indices removed)

• SAP Fiori as new User Experience

• Substantially reduced data footprint

SAP S/4HANA is delivered in two different deployment models:

• Cloud

• On Premise

SAP BTP implements the Digital Platform and is an enterprise platform-as-a-service that provides comprehensive application development services and capabilities, which lets you build, extend, and integrate business applications in the cloud.

It is supported by multiple cloud infrastructure providers and enables innovative technologies such as the Internet of Things, machine learning, artificial intelligence, and big data,

Key aspects of SAP BTP are f.ex. User Experience (SAP Fiori), SAP Cloud Identity Services, Domain Models and Master Data Integration, SAP Analytics Cloud, Environments (Cloud Foundry, ABAP, Kyma) and Security.

SAP BTP is available in many regions around the globe. You can choose between data centers hosted by SAP and those run by our partner Infrastructure-as-a-Service (IaaS) providers (so-called Hyperscalers):

Microsoft Azure, Amazon Web Services, Alibaba Cloud, and Google Cloud Platform.

SAP offers the following deployment options (deployment types) for the current SAP Business Suite, as well as for SAP S/4HANA:

• On Premise

  In this common model, the customer acquires a license and installs the software in their own data center.

• Cloud

  In this model, the customer rents the software for a certain period of time. SAP deploys the software in the SAP-owned data center.

• Hybrid

  In this model, required applications are operated partially by the customer and partially by SAP in the Cloud. Both parts can be linked and integrated with each other.

• Mobile

  In this model, mobile devices access On Premise, or Cloud applications.

SAP offers the following cloud models:

Public Cloud

Public cloud software typically runs in a multi-tenant server, where multiple tenants, or customers share the resources of the server. This is similar to an apartment building where multiple tenants live within the same physical infrastructure and share certain resources, but each tenant has their own key to a secure unit within the building.

Maintenance of the building and apartment units is factored into the rent paid by tenants and taken care of when tenants need it. In public cloud, each customer's data and applications are hidden from the other customers, but because they are sharing certain resources and maintenance of the solution is taken care of by the cloud provider, public cloud is often the most affordable and efficient solution.

Private Cloud

Private cloud software typically runs in a single tenant server, where only a single tenant (customer) uses the resources of the server. Software runs in a private network protected by a firewall, similar to an on premise system. The main differences between private cloud and on premise is who has responsibility for maintaining the server, and the license for the software installed on the server.

For on premise, a customer purchases the server and is responsible for maintenance. For private cloud, a third party provider owns the server and is responsible for maintenance. A customer pays a subscription fee to access the server over the internet and install software. In some cases, one cloud provider maintains the server, and another provider maintains the software installed on the server.

For example, with SAP S/4HANA Cloud, private edition, SAP is responsible for maintaining the business software, but the customer can choose to have their software on a server in an SAP data center, or a server in a data center from one of our hyperscaler partners. In this case, the hyperscaler partner is responsible for maintaining the server.

Private clouds offer more flexibility and customization than public cloud. If public cloud is an apartment, private cloud is a single family home on a plot of land.

The following graphic explains and differentiates On-Premise, IaaS, PaaS and SaaS:

An example for IaaS is SAP's Managed IaaS Solution: SAP HANA Enterprise Cloud (HEC)

A two-tier ERP strategy is when a company implements different ERP systems for separate parts of the business. By combining two different deployments of SAP S/4HANA, a business can take advantage of the fast innovation in public cloud, while still allowing for a high degree of customization for strategic processes in the private cloud or on premise.

• Scenario 1: Headquarter & Subsidiary Model

  Headquarters runs a highly customizable on premise or private cloud ERP and subsidiary runs a standardized public cloud ERP with a specific scope.

• Scenario 2: Central Services Model

  Organization has a line of business spin-off running a standardized public cloud ERP- For example, Finance would be a separate legal entity and run in the public cloud as "Shared Services", with the rest of the business running on a highly customizable on premise or private cloud ERP.

• Scenario 3: Ecosystem Model

  Headquarters runs a highly customizable on premise or private cloud ERP and brings their subcontractor(s) or dealer(s) on a standardized public cloud ERP.