Business Continuity with RISE and BTP: part 2 – Technical Building Blocks in RISE
updated date: 31.Oct.2023 This blog is part of the Business Continuity with RISE and BTP blog series: part 1 – Concept Explained part 2 – Technical Building Blocks in RISE 👈 part 3 – Technical Building Blocks in BTP
4. Technical Building Blocks in RISE
RISE with SAP Private Cloud Edition is a ‘SaaS-like’ one-stop offering with managed IaaS services (considering hyperscaler reference architecture of SAP on Azure, SAP on AWS, and SAP on GCP), managed SAP Basis services, and application support. In this section, we won’t be discussing the commercial combinations or the exact same offerings in SAP RISE, but rather will just explain the technical building blocks of what makes running SAP on hyperscalers (Azure, AWS, and GCP) possible.
4.1. IaaS Level
Load Balancers are functioned for monitoring and failover. With load balancers, the active server failure and be detected, then the traffic can be redirected to the redundant server. Below table is a summary of load balancers been used in RISE with SAP. Here’s an example of how SSO request with High Availability works under load balancing in RISE.
|Azure||Azure Load Balancers|
|Azure Traffic Manager||
|AWS||AWS Elastic Load Balancer (ELB)|
|Google Cloud Load Balancer||
|SAP||SAP Web Dispatcher||
RISE with SAP Private Cloud Edition running on Azure, AWS, and GCP, consume hyperscaler native storage component. There native storage components are with built-in features/services of backup, replication (either synchronous or asynchronous), snapshot, and recovery.
|Azure||Azure Managed Disks||
|Azure NetApp Files||
|Azure Blob Storage|
|AWS||Elastic Block Storage (EBS)||
|Elastic File System (EFS)||
|Simple Storage Services (S3)||
RISE with SAP Private Cloud Edition running on Azure, AWS, and GCP, consume hyperscaler native compute resources, and have been fully virtualised.
|Azure Virtual Machine||
|Google Compute Engine||
4.2. Operating System Level
Clustering solution on OS level for high availability and disaster recovery purpose failover.
|SUSE Linux (SLES) Pacemaker|
|Redhat Linux (RHEL) PowerHA||
|Microsoft Windows Server Failover Cluster|
4.3. Application and Database Level
4.4. IaC and CI/CD pipeline
When deploying hyperscaler infrastructure resources, with IaC enabled, the provisioning of infrastructure can be through code instead of through manual processes.
For application code change, CI/CD pipeline is recommended to automate and govern change management. This is especially necessary when doing side-by-side extensibility to keep the core clean. Below is a summary of available CI/CD pipeline services:
|SAP Continuous Integration and Delivery
(on SAP BTP)
|Google Cloud Build||
- The blog content does not necessarily represent the official opinion of SAP, Microsoft, Amazon Web Services, or Google Cloud. The opinions appearing in this blog are backed by SAP, Azure, AWS, GCP documentation which can be revealed in the corresponding reference links.
- The blog content is only focusing on technical discussion, hence can not be used as commercial basis, nor should be used as SAP official offering documentation.
Acknowledgment to contributors/reviewers/advisors:
Ke Ma (a.k.a. Mark), author, Senior Cloud Architect, RISE Cloud Advisory RA group
Special THANK YOU to RISE with SAP community members, who contributed to this blog:
Ferry Mulyadi, Partner Solution Architect, Amazon Web Services
Micah Waldman, Product Management Lead, Google Cloud Business Continuity
Thorsten Staerk, Customer Engineer, Google Cloud
Frank Gong, Digital Customer Engagement Manager, SAP ECS
Marc Koderer, Chief Architect, SAP ECS
Boris Maeck, Head of Technology and Architecture, SAP ECS
Aaron Smyth, Principle Service Architect, SAP
Sven Bedorf, Head of Cloud Architecture & Advisory, RISE Cloud Advisory, MEE
Kevin Flanagan, Head of Cloud Architecture & Advisory, RISE Cloud Advisory, EMEA North
Luc DUCOIN, Cloud Architect & Advisor Expert, RISE Cloud Advisory, EMEA North
Richard Traut, Head of Cloud Architecture & Advisory, RISE Cloud Advisory, EMEA North
Peter van den Berg, Cloud Architect & Advisor Expert, RISE Cloud Advisory, MEE
Extended Reading: case study: extra-large scale HANA DB sets in RISE S4 PCE, by SAP ECS colleague Marc Koderer SAP on Azure documentation, by Microsoft SAP on Google Cloud documentation, by Google Cloud Some more previous blogs: DNS integration with SAP RISE in multi-cloud environment series guide – Azure DNS integration with SAP RISE in multi-cloud environment series guide – AWS DNS integration with SAP RISE in multi-cloud environment series guide – GCP Harmonized Single Sign-On for SAP RISE Customers in Multi-Cloud Environment Demystify Single Sign-On on Server Side for SAP RISE Customers empower SAP RISE enterprise users with Azure OpenAI in multi-cloud environment Unlock the Power of Business Data for SAP RISE Customers: Mastering Data Management and Cultivating Insights Extend the Power of Data for SAP RISE Customers: data federation with SAP in multi-cloud GCP Extend the Power of Data for SAP RISE Customers: data federation with SAP in multi-cloud AWS Extend the Power of Data for SAP RISE Customers: data federation with SAP in multi-cloud Azure