introduction to cloud technology from sap for application ......• sap cloud platform (for...
TRANSCRIPT
PUBLIC
New Town Square: Janko Budzisch, SAP // Heidelberg: Janko Budzisch, Christian Niedermayer, SAP
November, 2019
Introduction to Cloud Technology from SAP forApplication Lifecycle Management Professionals
2PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Introduction Cloud Technology
Some concepts of SAP Cloud Platform
Some implications for SAP Cloud ALM
Agenda
Introduction
Cloud Technology
4PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Cloud Benefits for Customers
Always
available
Always
up to dateUnlimited
scalability
No IT
maintenance
costs
Access from
anywhere
Maximum
efficiency
Why Cloud?
5PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
No IT
maintenance
costs• Software as a service (SaaS)
• Provide a complete application to end users. Customization and own user management possible.
• ByDesign, SuccessFactors, FieldGlass, Cloud 4 Customer, Ariba, Hybris, Concur, S/4 Hana Cloud
• SAP Cloud Application Management (CALM)
• Platform as a service (PaaS)
• Development and lifecycle management platform including core components (e.g. DB) for building new apps.
• SAP Cloud Platform (for customers extending SAP solutions, for custom developments, as a platform for SAP SaaS solutions)
• Amazon Web Services, Google Cloud Platform, Microsoft Azure, Alibaba Cloud
• Infrastructure as a service (IaaS)
• Provide processing, storage and network. OS and all on top is managed by the customer.
• Amazon Elastic Compute Cloud, Google Compute Engine, Microsoft Azure Virtual Machines
PCloud Service Models
6PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Example: Data Centers for SAP Cloud Platform
• Alibaba planned for 2020
• Not all services are offered in each data center→ Cloud Foundry isn‘t offered in SAP data centers
→ CALM starting in AWS Frankfurt, expansion driven by demand
Via Internet / web browser
Access from
anywhere
P
7PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Example: Support & Deployment for SAP Cloud Platform
SCP Cloud Cockpit
SCP Job Scheduler
Always
availableP
SCP HANA Tools
SCP Audit Log Viewer
Log Viewer (Kibana)
Performance Monitor (Dynatrace)
Sufficient monitoring and support to avoid
unplanned down times
Temporary operation of as-is
and to-be code level to avoid planned down times
To-Be
Code
Level
As-Is
Code
Level
Log
OutLog
In
True zero down time powered by
Deploy with Confidence
Deployment
1
23
8PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
PUnlimited
scalability
A
C
B
D
A
C
B
D
A
C
B
D
A A
BA
Example: Monolith vs. Micro service based Architecture
Monolith Architecture Micro service based Architecture
C
D
Each micro service runs in separate process / container:
• Be deployed individually and frequently
• Scale independantly to varying loads (if possible automatically)
9PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Example: Deploy with confidence (DwC)
• Optimized for cloud-native micro service applications
• Focus on fast and frequent delivery, powered by:
• Dynamic Request Routing
• Testing in production like environments
• Feature Toggle Management
• True zero-downtime for consumers
• Includes Best-practice templates for
• Onboarding
• Business Configuration
• Documentation/user assistance
Code& test
Integrate& promote
Release& deliver
Validate,configure
& run
App Dev teams(SAP, Partners, Customers)
Acceptancetest
team
Release engineering team
Customeradoption
team
on commit
continuouslydaily
as desired
“Develop features within distributed applications with ease and deliver them with confidence on a daily basis!”
Always
up to date
P
10PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Example: SAP Cloud Application Programming Model Maximum
efficiency
P
Some concepts of
SAP Cloud Platform
12PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
SAP Cloud Platform - High level architecture
13PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
SAP Cloud Platform - Cloud Foundry
14PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
SAP Cloud Platform - Landscape Design
15PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
SAP Cloud Platform - Domain Model
16PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
SAP Cloud Platform - Multi-Tenancy
17PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
SAP Cloud Platform - User Management per Tenant
18PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
SAP Cloud Platform - Tenant Data Separation Options
One DB instance with one DB
schema shared by alltenants.
Tenant separation by discriminator
column in each tableTenant id to be entered in each table
access statement. Same DB userfor all tenants.
Tenant move is difficult.
Resources (CPU, memory, disk) shared by all tenants.
Multi Database Container
Schema
Instance
Table11
22
1
Discriminator Column
Customer 1 / Tenant 1
Customer 2 / Tenant 2
Multi Database Container
Instance
Schema Schema
Table Table
Schema Separation
One DB instance with separate DB schema per
tenant.Separate DB users per schema with access to own
schema only.
Resources (CPU, memory, disk) shared by all tenants.Tenant move is relatively easy.
In SCP this type of separation is especially supported by
HDI containers (HDI = Hana Deployment Infrastructure).
Each schema shown above is managed by one HDIcontainer.
Customer 1 / Tenant 1
Customer 2 / Tenant 2
Multi Database Container
Schema
Instance 1
Schema
Instance 2
TableTable
Instance SeparationOne DB instance with separate DB schema per
tenant.Separate DB users per schema with access to own
schema only.
Tenant move is very easy.Private resources (CPU, memory, disk) per tenant.
Customer 1 / Tenant 1
Customer 2 / Tenant 2
Some implications for
SAP Cloud ALM
20PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
SAP Cloud ALM - Cloud Services offered via SAP Cloud Platform
21PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Open Open & Opinionated Opinionated
SAP Cloud Platform Foundation
Other (React,…)
Other (Spring,…)
Other (Postgres,…)
Integrate with
Other (Kubernetes,..)
…
Build on
DevOps+
LCM
Extension
Services
Events
Models
Replication
Interoperability
Reuse of Skills
OData, REST OData, REST
SQL SQL
SAP Fiori/Ul5 SAP Fiori/Ul5
SAP HANA SAP HANA
OData Libraries (Java, Node)
Cloud App. Programming Model
Core Data
Services
Java/Node
Frameworks
SAP Cloud
SDK
OData Protocol (ABAP)
ABAP RESTful Programming Model
Core Data
Services
ABAP
Frameworks
ABAP
Development
General EnterpriseCloud Developer
SAP-focusedCloud Developer
ABAP developer
StartupDeveloper+ Citizen
Developer +
1
1) planned innovations / future direction
Cloud FoundryTechnical Environment
chosen for SAP Cloud
ALM
SAP Cloud ALM – Selected development paradigm
22PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
CALM Global Customer Account 1
CALM Global Customer Account 2
CALM Global Customer Account 3
SAP Cloud ALM - Subscription Model and Cross Customer Data Access
CXS Global Provider Account
CALM Provider Sub Account
Subscription Customer 1
Subscription Customer 2
Subscription Customer 3
HDI #3
HDI #2
HDI #1
Customer Sub Account 1
Customer Sub Account 2
Customer Sub Account 3
HANA MDC
ContentTemplates
Docu
BestPractic
HDI #X
CALM Global Provider Account
SAP Cloud Platform• Every customer with appropriate
Enterprise Support / Cloud Subscription contract will be entitled to use SAP Cloud ALM (limited by resource quota)
• If customer decides to use SAP Cloud ALM appropriate CALM Global Customer account and CALM Customer sub account will be generated (independently from existing SCP accounts)
• CALM Customer Sub Account subscribes to CALM application running in one specific CALM Provider Sub Account
• CALM Global Provider Account and associated CALM Provider Sub Accounts are owned by SAP
• CALM Provider Sub Accounts are specific for one SCP data center and represents the actual physical resources ➔All other accounts have pure logical character
Account structure chosen
for SAP Cloud ALM
23PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
SAP Cloud ALM - Realization of Resilience on Persistency Level
Multi Database Container
Instance
Schema Schema
Table Table
Without Persistency Resilience
• All use cases and their microservices use the same schema (HDI container).
• If this schema (resp. the hosting DB instance) is not available no use case is working.
Customer/Tenant 1
Customer/Tenant 2
Multi Database ContainerMulti Database Container
Instance
Schema
Feature 1
Table Table
Schema
Feature 1
Instance
Table Table
Schema
Feature 2Schema
Feature 2
With Persistency Resilience• For each use case and reuse services with own persistency use separate schemas
(HDI containers) for their persistency.
• This enables resilience from development level (independent logical persistency stores). For achieving „physical“ resilience those separate use case specific schemas have to be located within separate DB instances.
• The resource overhead of an HDI container is very low. Moving all customers data from one place to another (e.g. to another data center) will be more difficult with separate schemas, however automation is requested.
Customer 1 / Tenant 1
Customer 2 / Tenant 2
Feature 1 / Domain 1
Feature 2 / Domain 2
Persistency model chosen
for SAP Cloud ALM
24PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
SAP Cloud ALM - SAP Cloud Application Programming Model
Programming model chosen
for SAP Cloud ALM
25PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
SAP Cloud ALM for Operations – Semantical Services
Data Consistency
Management Service
Exception
Monitoring Service
Use case
services
Re-use
services
Infrastructure
services
Cross use
case services
Performance
Monitoring Service
Integration
Monitoring Service
Synthetic User
Monitoring Service
Real User
Monitoring Service
Business Process
Monitoring Service
Job
Monitoring Service
End-to-End Event &
Alert Management Service
End-to-End Operation
Automation Service
End-to-End Analytics
& Intelligence Service
Data Collection
Push Service
Data Collection
Pull Service
Landscape
Management Service
Notification
Management Service
Business Process
Improvement Service
Configuration
Monitoring Service
Availability
Monitoring Service
Business Service
Management Service
System
Monitoring Service
Root Cause
Analysis Service
26PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ
SAP Cloud ALM for Operations – High Level Architecture
Join the SAP Digital Business
Services LinkedIn group for
networking and updates!
Follow us on Twitter (#solman and
#CloudALM), get the latest news,
learn about support offerings and
events!
Search for “SAP Cloud ALM” on
YouTube for product demos, expert
interviews and event insights!
Join our social media family
Subscribe to WhatsApp SAP Product
Support channels and receive updates
including KBAs, wiki's, guided
answers, SAP Notes and “hot tips”.
Thank you.
Contact information:
Janko Budzisch
Chief Product Owner
Christian Niedermayer
Cross Architect