Enterprise PaaS, Cloud-Native Architecture and Microservices

©"2016"IBM"Corporation
Florian"Georg
IBM"Cloud"Advisor
florian.georg@ch.ibm.com
@florian_georg
EnterpriseEPaaS"and"
CloudENative"Architecture
Guest"Lecture"E University"Zurich

2Page©"2016"IBM"Corporation
Agenda
Introduction
Enterprise"PaaS
Cloud"Native"Architecture
Microservices

Agenda
Introduction
Enterprise"PaaS
Microservices

The"Different"Cloud"Delivery"Models
Traditional
on premises
Applications
Data
Runtime
Middleware
O/S
Virtualization
Servers
Storage
Networking
Infrastructure
as a Service
(IaaS)
Applications
Data
Runtime
Middleware
O/S
Virtualization
Servers
Storage
Networking
Platform
as a Service
(PaaS)
Applications
Data
Runtime
Middleware
O/S
Virtualization
Servers
Storage
Networking
Software
as a Service
(SaaS)
Applications
Data
Runtime
Middleware
O/S
Virtualization
Servers
Storage
Networking
Customer managed
IBM managed
Standardization; lower costs; faster time to value

TwoEspeed"/"biEmodality"of"modern"IT
Different"layers"and"
workloads
IT"workloads"emerge"
and"evolve"at"different"
speeds.
Analysts"predicts"75%"of"IT"orgs"will"
have"a"biEmodal"capability"in"2017

Systems
of
Innovation
Systems
of Record
New$Projects: The"speed to drive
innovation and growth
Traditional$Projects: The"capabilities to
capitalize on"your institutional knowledge
Agile
Edge
Industrialized
Core
Hybrid$Integration
Successful$hybrid$clouds$deliver:
‒ Developer$productivity
‒ Integration$and$portability
‒ Data$and$analytics
‒ Visibility,$control$and$security
Hybrid"Cloud:"Integrate"Clouds"and"OnEPremises

http://www.cloudcomputingpatterns.org/Elastic_Platform
Customer Development Operations

Different"Levels"of"Abstraction

Use"Cases"for"PaaS"in"an"Enterprise"Context
– Innovation"platform"(developer"centric)
– Hybrid"Integration,"securely"consume"public"services
– Systems"of"engagement,"Mobile,"IoT …"
– User"Experience"(UX)"and"lean"experimentation
– SaaSify existing"applications
– Small"“backoffice”"apps"(“The"Long"Tail”)
– Building"Partner"ecosystem"/"dev"collaboration
– API"Layer"/"API"economy

Use"Case"#1:"Modernization"+"Backend"Integration
– Improved"Agility"&"
Time"to"market"for"
new"capabilities
– Improved"lifecycle"
management"and"
faster"dev/ops"
turnaround
– Modernization"(e.g."
new"Frontends"/"
Systems"of"
Engagement)
– Highly"scalable"API"
or"frontend"layer"for"
backend"systems
– Keep"compliance"
and"data"locality
Legacy"
Application
Backend
New"
Capabilities
Secure"connection"
/"API
! traditional Cloud""

Use"Case"#2:"CloudEnative"reEarchitecturing
– Build"true,"
scalable" multiE
tenant"SaaS"
solutions
– Highly" improve"
fault"tolerance"and"
resiliency" of"
architecture
– Manage"
complexity"of"
product"portfolio
Legacy"
Application
S1
S1
S3
S1
S4
S2
S3S3S3

Use"Case"#3:"Hybrid"dev/prod"for"2Espeed"IT
E Agile"prototypes,"
pilots,"explorations"
and"PoCs
E Option"to"operate"in"
managed"environment"
for"production
E Introduce"and"validate"
new"features"and"
versions"quickly
E Seamless"migration"
between"clouds
Idea"/"
Project"/"
New"
Capability
Dev
Bluemix Public"E off"premises
Test
Prod
Bluemix Local"E on"premises
Speed
Control
Focus:

IoT
IBM’s"Open"Cloud"Architecture"E Technologies
DevOps
Runtimes
OAuth
Security
Web$and$Mobile Data$and$Analytics
Operating$ Environment

CloudFoundry:"Pushing"Code"
Buildpack
(“Runtime”)
Droplet
cf push
Developer
(or"delivery"pipeline)
Source
Application"
(n"instances)
Workstation"/"Buildserver Bluemix PaaS
Router
User
https://myapp.url
Staging Execution
Environment
run"on
DEAs
(="VMs)
loadE
balance"
1..n

Agenda
Introduction
Enterprise"PaaS
Microservices

What"kind"of"a"motivation"do"we"have?
– Start"small,"scale"fast
– Minimize"upfront"invest"E pay"as"you"scale
– Minimize"Risks"(financial,"productEmarket"fit,"technical"feasability)
– Build"for"multiEtenancy"(SaaS)
– High"Availability"at"(potential)"massive"scale
– Agility"and"Speed
• Time"to"Market
• Minimize" Risk
• Cut"costs"(yes!)
– Leverage"new"technologies"and"services
– Support"a"devOps culture"(Conway’s"Law)

Culture
Foundational
values"and"principles
Think
Conceptualization,"
refinement,"and"
prioritization"of"
capabilities
Code
Generation,"
enhancement,"
optimization"and"
testing"of"features
Deliver
Automated"
production"and"
delivery"of"
offerings
Run
Services,"options,"
and"capabilities"
required"to"run"in"
the"Cloud
Manage
Ongoing"
monitoring,"
support,"and"
recovery"of"
offerings
Learn
Continuously"
learn"based"on"
outcomes"from"
experiments
Combining"industry"best"practices"for"
Design$Thinking,$Lean$Startup,$
Agile$Development,$DevOps,$and
Cloud$to"build"and"deliver"innovative"
solutions.
To"learn"more"visit:
https://www.ibm.com/devops/method
IBM"Bluemix Garage"Method

Architecture"Principles
– Twelve"Factor"Apps
– Cattle"vs"Pets"(MTTF"vs."MTTR)
– Resiliency
• Reactive"programming
• Design"for"Failure
• Immutable"Services
• Resiliency" Testing
• SelfEhealing" systems

http://12factor.net/

Cattle"vs"Pets
E Servers"get"unique"names"
(‘homer.mynetwork.com’)
E Hand"raised"and"cared"for
E If"gets"sick,"we"nurse"them"
back"to"health
E Servers"get"numbers"and"are"almost"
identical"(‘f023eaE232.mynetwork.com’)
E If"they"get"sick,"we"shoot"them"and"clone"
another"one"vE)"

Availability"="MTTF"/"MTBF"="MTTF"/"(MTTF"+"MTTD"+"MTTR)
4/25
Different"approaches"to"HA
Source:"
http://www.slideshare.net/d0cent/monitori
ngEwithEnagiosEandEganglia
CloudLnative:" minimize
(MTTD"+"MTTR)
Traditional:"Maximize"
MTTF

http://www.reactivemanifesto.org/

Example"concept:"
UI"Latency"Compensation
Instant"UI"updates
ClientEside"data"replica
From:"https://meteorhacks.com/introductionEtoElatencyE
compensation.html

Design"for"Failure:"Circuit"Breaker"Pattern
See"also: https://www.ibm.com/devops/method/content/manage/practice_circuit_breaker_pattern/
http://martinfowler.com/bliki/CircuitBreaker.html
• Always"Anticipate" failures
• Minimize" “blast"radius”
• Graceful"degradation" of"service

Immutable"Services
– NonEdestructive"
production"updates
– Service"versions"get"
installed"sideEbyEside
– Crucial"for…
• Canary"Testing
• Blue/Green"
Deployments
• A/B"Testing
• Service"Versioning

Resiliency"Testing"and"SelfEhealing

Foundational"services"and"solutions

Bluemix Architecture"Center
https://developer.ibm.com/architecture/gallery

Scenario Implementation

Agenda
Introduction
Enterprise"PaaS
Microservices

Characteristics"of"Microservices
– Componentization
– Business"Capabilities"vs"Technical"Layers
– Design"for"Failure
– Smart"Endpoints,"dumb"pipes
– Decentralization
– Automation

Microservices
Source:"http://martinfowler.com/articles/microservices.html

Monolith"to"Microservices E Example
DB
Run3time
Orders"service
Shipping"service
Catalog"service
Storefront"
UI
Run3time
Run3time
Run3time
DB
DB
Microservice Based
Prox
y
Application
DB
Middleware
Storefront"UI
Orders
service
Shipping"
service
Catalog
service
Monolith

Conway’s"Law
Any8organization8that8designs8a8system8(defined8broadly)8will8produce8
a8design8whose8structure8is8a8copy8of8the8organization's8
communication8structure.
33 Melvyn8Conway,81967

CrossEfunctional"teams"per"Business"Capability
Source:"http://martinfowler.com/articles/microservices.html

Monolith"vs"Microservices
–Partial"Deployment
–Availability
–Promote"strong"module"
boundaries"(Network)
–Multiple"platforms
–Simplicity
–Consistency
–Easy(ier)"refactoring

The"Microservices Premium
Source:"
http://martinfowler.com/bliki/MicroservicePremium.html

Microservices ”Compute”:"Containers
– Application"
Container"
(Docker,"rcket
– Lightweight"&"
Fast
– Not"a"new"
technology,"but"
Docker"made"it"
”consumable”"by"
Dev"teams
– Still"considered"
immature"for"
enterprise"
workloads

Patterns"and"Automation
– “Infrastructure"as"Code”:"Describe"target"
environments
– Automate"provisioning"(Chef,"Puppet,"
Ansible,"IBM"Cloud"Orchestrator,"Docker"
Machine..)
– Automate"Deployment"(urbancode
deploy,"Docker"Swarm,"Kubernetes,"
Mesos/Marathon"…)

Microservices:"Datastores
– Impedance"Mismatch"
between"“Objects”"and"
RDBMS
– Scaling"RDBMS"across"
clusters"is"a"complex"
task
– NoSQL"databases"
• Broad"range"of"different"
approaches
• Horizontal" scaling
• Broad"Open"Source"
ecosystem

Characteristics"of"NoSQL"Datastores
– NonErelational
– Horizontally"scalable"(massive)
– SchemaEless
– CAP"Theorem"(*)
• Consistency (all"nodes"see"the"same"data"at"the"
same"time)
• Availability (every"request"receives"a"response"about"
whether"it"succeeded"or"failed)
• Partition8tolerance (the"system"continues"to"operate"
despite"arbitrary"partitioning"due"to"network"failures)
– Popular"for"cloudEnative"/"Microservices:
Many"lean"towards"Partition"Tolerance"" good"fit"for"
distributed"architectures"like"Microservices
http://i.stack.imgur.com/Hx8h0.png
(*)"Wikipedia

Types"of"NoSQL"Databases
– Document
– KeyEValue
– ColumnEoriented
– Graph"DBs
– …

SchemaEless
– Easier"to"migrate
– Easier"to"change
– Still:"implicit"schema
" data"consistency"becomes"an"“application"level"responsibility”,"
instead"of"a"DB"feature."Which"is"a"good"thing.

Data"Modeling"Tradeoffs
– Most"NoSQL"databases"(except"GraphDBs)"
store"aggregated"objects
– Beneficial"for"more"clear,"bounded"data"
abstractions"that"are"relativly stable
– May"be"painful"for"dynamic,"multiEdimensional"
analytics"(slide"&"dice"/"group"/"pivot"/"view"E
operations)

Common"Challenges"with"Microservices
– Isolation"&"Security"concerns
– API"Versioning
– System"complexity
– Need"a"devOps culture

Requests A
B
DevOps
Services
B
’
Data$Plane
Authentication,"Provisioning,"Resource"Management,"Service"
Registration,"etc.
Red/Black"Deploy,"
A/B"testing
e.g.,%send%70%%to%
B,%30%%B’
Control$Plane
Resiliency"
Testing
D
’
D
e.g.,%overload%D’%and%
check%for%circuit%
breaker%at%B’
Service8
Proxy
Microservice"
instances
Edge8
Router
Microservice"Applications"– IBM"Point"of"View
App$Deployment

A"Microservice"App"on"IBM"Bluemix
51
Orders
Catalog
UI
Sd
RuleLbased
Routing$$&
Load$Balancing$ $
S
p
Service$ Registratiion
&$Heartbeat.
Automatically$ deletes$
unhealthy$ instances
SQLDB
service
Cloudant
Bluemix Services
(Liberty)
(Liberty)
(nodeJS)
Bluemix E ContainersBluemix E Cloud"Foundry""
1."I"want"to"update"my"UI"Microservice without"any"disruption"
Deployment$ +
Roll$Forward$
based$ on$analytics
Ad
(+Canary"
Advisor)"
UI’
2."I"want"to"use"comparative"analytics"to"decide"if"to"Roll"Forward"
Go"Router
3."I"want"to"systematically"test"for"failure"recovery"before"going"live
(Liberty)
Gremlin
Bluemix Control"Plane
Systematically$ test$for$
failure$ recovery$ in$
testing/production$
environments

Summary
– Enterprise"PaaS
• What"?"Why"?
– CloudEnative"Architecture
• Principles
– Microservices
• Characteristics
• “Cattle”:"Containers
• Decentralized" Data"/"NoSQL

Thanks
by"xkcd

Enterprise PaaS, Cloud-Native Architecture and Microservices

More Related Content

What's hot

Viewers also liked

Similar to Enterprise PaaS, Cloud-Native Architecture and Microservices

More from Florian Georg

Recently uploaded

Enterprise PaaS, Cloud-Native Architecture and Microservices