SAP on Hyperscalers – Strategy, Architecture, and Deployment

Unit 8: Runtime Considerations

Runtime Considerations
Change management in the cloud

▪ Keep in mind, the hyperscaler releases

new features at more frequent intervals
than the traditional releases of the past
▪ Your team has had to learn to be agile –
both literally and metaphorically
▪ Automation could enable your team to cut
back on human error, improve SLA, and
in many cases, implement a self-service
approach for internal customers to deploy
themselves
Cloud services
▪ Automating incidents and change hyperscaler and hyperscaler
management is now possible with the global
infrastructure
multiple tools available

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Runtime Considerations
Testing strategy becomes part of change management

▪ A regression testing strategy should be mandatory for new features and updates applied to the cloud
instances
▪ Keep in mind, most hyperscalers require that you get approval before executing a performance test
▪ Backout plans can be fully automated in the cloud to restore back to previous image
▪ However, standard testing principals for the SAP application still apply

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Runtime Considerations
Upgrades or changes in the cloud

N N
N
DPS QPS PRD
N N N

(at cutover)
DEV (N+1) QA (N+1)
(N+1)
N+1 N N+1 N

Canary or green-blue architecture might be ideal for clean systems on a hyperscaler

▪ On hyperscalers, we are able to spin up some systems and use them as needed from a cost perspective
– Great way of making sure the original transport route is being used for break/fix solutions
– Typically not ideal for large system requiring bare metal unless this is a current requirement
▪ Use the N+1 landscape for service packs and other significant upgrades without interrupting the production landscapes

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Runtime Considerations
Cost considerations

N
DPS QPS PRD
N N N

Cost allocation
Business
System

Business requirements and new features can be tested individually

▪ On hyperscalers, we are able to spin up some systems and use them as needed from a cost perspective
– Cost allocation is easily understood and can be charged back to business unit or cost center on a per-use basis
– Requirements and systems can easily be replicated for the business units that need to evaluate new features
– Additional systems can be brought up in a development network zone for robust security considerations
– All versions are equivalent to the production landscape and new features can be tested directly in the production
environment
– Environment can be sunset at customer’s request, reducing the investment and cost for the environment
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5
Runtime Considerations
Personas

IT Architect Cloud Architect Basis Administrator

▪ Expert understanding of the ▪ Expert understanding of the hyperscaler
hyperscaler management tools, e.g. management tools, e.g.
− Management console for − Management console for provisioning and
provisioning and managing managing hyperscaler resources
hyperscaler resources − Monitoring tools
− Monitoring tools − Log resources
− Log resources ▪ Good understanding of networking: TCP/IP,
▪ Understanding the connection IP addresses, HTTP, DNS
between on-premise and hyperscaler ▪ Security in the cloud is important, and
▪ Interface design and configuration consequently, a high-level understanding of
key security concepts is a must for a cloud
architect
▪ Certified for a specific hyperscaler
▪ Expert understanding of the hyperscaler
management tools, e.g.
− Management console for provisioning
and managing hyperscaler resources
− Monitoring tools
− Log resources
▪ Same skills as the on-premise world to
manage the SAP instances on the
hyperscaler

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Runtime Considerations
Personas

Security Network Architect Administrator

▪ Expert understanding of identity ▪ Expert understanding of the hyperscaler ▪ Expert understanding of hyperscaler
management solutions management tools, e.g. pricing and provisioning
▪ Understanding the connection − Management console for routing and ▪ Relationship with hyperscaler for correct
between on-premise and hyperscaler connectivity setup and configuration
▪ Expert understanding of VPN for − Monitoring tools ▪ Delegation of on-call and resolution
connections from on-prem to − Firewalls management
hyperscaler ▪ Expert understanding of networking: TCP/IP,
▪ External access concepts if required IP addresses, HTTP, DNS
▪ Encryption technologies as needed ▪ Security in the cloud is important, and
consequently, a deep understanding of
firewalls and traffic flow is required

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2020 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/copyright for additional trademark information and notices.