Critical business use cases built on SAP BTP need to be highly available and responsive. While availability zones help with disruptions in a single region, application developers and administrators are responsible for availability and stability in cases of regional outage or application upgrades. This scenario demonstrates techniques for load balancing, failover, and latency reduction of SAP BTP services, such as SAP Launchpad and SAP Cloud Integration, with Hyperscaler traffic management solutions like Azure Traffic Manager & Amazon Route 53.
A lack of automatic failover, especially for critical business scenarios, can be damaging to your business. If users are located in diverse geographies, latency will also increase if services are restored in a single region.
Use your own domain for SAP BTP services, extensions, and integrations endpoints using the SAP Custom Domain Service. Configure Hyperscaler traffic management solutions such as Azure Traffic Manager and apply different profiles to decouple connection information.
A cloud-native integration pattern that incorporates SAP BTP and Hyperscaler services eliminates downtime, reduces global latency, and increases throughput.
In this scenario, you will learn how to achieve the high availability of a Cloud Integration flow built by a customer using SAP Custom Domain service & Azure traffic manager.
This scenario will be similar to the above one, but here we will achieve the high availability of the SAP Launchpad service, a SaaS application managed by SAP.
Create an issue in this repository if you find a bug or have questions about the content.
For additional support, ask a question in SAP Community.
If you wish to contribute code, offer fixes or improvements, please send a pull request. Due to legal reasons, contributors will be asked to accept a DCO when they create the first pull request to this project. This happens in an automated fashion during the submission process. SAP uses the standard DCO text of the Linux Foundation.
Copyright (c) 2021 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.