Case Study: How to move from a Monolith to Cloud, Containers and Microservices

Kai Wähner
Technology Evangelist
kontakt@kai-waehner.de
LinkedIn
@KaiWaehner
www.kai-waehner.de
TIBCO Meetup Mumbai, India (February 2017)
Case Study:
How to move from a Monolith to Cloud, Containers and Microservices

© Copyright 2000-2017 TIBCO Software Inc.
Evolving Demands from the Business
AGILITY &
SPEED
REDUCED
CYCLE
TIMES
WEB
SCALE
LOWER
COST
FAIL FAST

• A cloud-native architecture enables flexible and agile development
• Only vendor- and platform-agnostic architectures are future-safe
• Various programming languages, open source frameworks and middleware
complement each other well in a Microservices world
Key Takeaways

1) A Legacy Monolith Application
2) The Move to Microservices
3) The Need for a Cloud Native Platform
4) Cloud Native Microservices
5) Live Demo with Docker, Kubernetes, Cloud Foundry
Agenda

Big and Complex Monolith
Monolith 1
„Big SOA Application“
(Middleware + Java)
Monolith 2
Monolith 3
CRM ERM Host ...
Virtual Machine(s)
Cloud-Ready
On Premise
Public Cloud

#1
On premise will not die.
Not everything will or should go to the cloud!

Various Technologies Glued Together
Middleware

Development Environment
Zero
Coding
Code
Everything
or anything in between

#2
Visual coding works,
even for very complex scenarios.
It can be combined with coding, too!

© Copyright 2000-2017 TIBCO Software Inc. 12
Microservices Example
http://www.ibm.com/developerworks/cloud/library/cl-bluemix-microservices-in-action-part-1-trs/
Each tile is a microservice
“bookflights” interacts
with other microservices
Height corresponds to usage
Each microservice can be
Independently managed
à Shorter time to results and increased flexibility / scalability
à Replace small pieces instead of a complete application

From a Monolith to Microservices
Business
Service A1
Java
Cloud-Ready
On Premise
Public Cloud
CRM ERM Host ...
Business
Service A2
Python
Integration
Service A3
Middleware
Business
Service B1
Java
Business
Service B3
Python
Business
Service B2
Go
Integration
Service B4
Middleware
Virtual Machine(s)

Various Forms of (Micro)Services
Integration
Service
Monolith application SOA
Integration
Service
Service ServiceService Service
SaaS Service BPM Service

Distributed Microservice Architecture
http://blogs.gartner.com/gary-olliffe/2015/01/30/microservices-guts-on-the-outside/
”That complexity
has moved and
[…] increased [to]
the outer
architecture.”

New Challenges Emerging…
http://highscalability.com/blog/2014/4/8/microservices-not-a-free-lunch.html
”[…] when considering Microservice like architectures, it's really important to not be attracted
to the hype on this one as the challenges and costs are as real as the benefits."
• Different Languages / Technologies
• DevOps Skills Required
• Distributed System Complexity
• Distributed Configuration
• Service Discovery
• Resiliency
• Client Side Load Balancing
• Testability Challenges
• Orchestration / Integration
• Spaghetti Communication (again ?!)
• Re-Delivery
• Re-Route
• Cache
• ...

New Design Patterns Emerging…
Resilience Design Patterns
Features
• Fail fast and rapidly recover
• Prevent cascading failures
• Latency tolerance logic
• Fault tolerance logic
• Fallback Options
http://martinfowler.com/bliki/CircuitBreaker.html
https://github.com/Netflix/Hystrix/wiki
maxFailures = 5
resetTimeout = 1min
callTimeout = 10s
à maxFailures++
Example: Circuit Breaker

#3
Microservices are not free lunch.
They do not fit into every scenario!

Open API and API Management

New Design Patterns Emerging…
http://samnewman.io/patterns/architectural/bff
https://www.thoughtworks.com/insights/blog/bff-soundcloud
Example: Backends for Fronteds (BfF)
?

A
P
I
M
A
N
A
G
E
M
E
N
T
From Microservices to Open APIs
Business
Service A1
Java
Cloud-Ready
On Premise
Public Cloud
CRM ERM Host ...
Business
Service A2
Python
Integration
Service A3
Middleware
Business
Service B1
Java
Business
Service B3
Python
Business
Service B2
Go
Integration
Service B4
Middleware
API
API
Virtual Machine(s)

#4
Design Microservices
with open APIs in mind!

“Cloud washing is the purposeful and sometimes deceptive
attempt by a vendor to rebrand an old product or service by
associating the buzzword ‘cloud’ with it [and offering it via a
public cloud infrastructure].”
Cloud Washing vs. Cloud Native
http://searchcloudstorage.techtarget.com/definition/cloud-washing
!

12 (or 13, 14, …) Factor Apps for Cloud Native Microservices
Codebase
One codebase
tracked in
revision control,
many deploys.
Dependencies
Explicitly declare
and isolate
dependencies.
Config
Store config in
the environment.
Backing
Services
Treat backing
services as
attached
resources.
Build, Release,
Run
Strictly separate
build and run
stages.
Processes
Execute the app
as one or more
stateless
processes.
Port Binding
Export services
via port binding.
Concurrency
Scale out via the
process model.
Disposability
Maximize
robustness with
fast startup and
graceful
shutdown.
Dev / Prod
Parity
Keep dev,
staging, and
prod as similar as
possible.
Logs
Treat logs as
event streams.
Admin
Processes
Run
admin/mgmt
tasks as one-off
processes.
https://12factor.net/

• Scalable services
• Service Discovery
• Load balancing and failover
• Resiliency
• DevOps and automation
• Usage of public cloud platforms, but also private or hybrid
• Self-service, pay-as-you-use, multi-tenancy
• Vendor-agnostic deployment
Cloud Native (à not just Microservices)
à Focus on business problems

#5
Cloud-Native means much more
than a “cloud-washed” application
deployed to a cloud provider!

== The Momentum of Containers
How to deploy independent Applications or (Micro)Services?
Garden

Why Containers?
http://www.slideshare.net/andersjanmyr/docker-the-future-of-devops
Containers enable:
• Lightweight deployment
• Automation
• Better resource utilization
• Scaling up and down quickly
• Platform agnostic deployment
• Innovation and Fail Fast Concepts
• Standardization ? Ø The Open Container Initiative (OCI)
Ø Docker Fork Discussions (!!!)

A
P
I
M
A
N
A
G
E
M
E
N
T
From Microservices and Open APIs to Containers
Business
Service A1
Java
CRM ERM Host ...
Business
Service A2
Python
Integration
Service A3
Middleware
Business
Service B1
Java
Business
Service B3
Python
Business
Service B2
Go
Integration
Service B4
Middleware
API
API
Cloud-Ready
On Premise
Public Cloud
Container(s) Container(s) Container(s)

#6
Microservices and Containers are often used together,
but also work very well without each other!

Cloud-Native Architecture
Containers are just the Foundation
for a Cloud Native Architecture!

Cloud Native Landscape (created by CNCF)
https://github.com/cncf/landscape

Cloud Native Platform (Infrastructure-as-a-Service)
Choose your IaaS
Private or Hybrid Cloud
Reduced costs of Infra
Self-hosted & Controlled Env
Servers
Storage
Network
IaaS

Cloud Native Platform (Platform-as-a-Service)
Choose your PaaS / Container
Cloud-Native App Dev
Self-service agile
infrastructure
Elasticity & Scalability
OS & Containers
Scalability
Routing
Logging / Monitoring
PaaS

Cloud Native Platform (IaaS + PaaS)
Choose your IaaS
Choose your PaaS / Container
Private or Hybrid Cloud
Cloud-Native App Dev
Reduced costs of Infra
Self-service agile
infrastructure
Self-hosted & Controlled Env
Elasticity & Scalability
Servers
Storage
Network
OS & Containers
Scalability
Routing
Logging / Monitoring
PaaS
IaaS

Kubernetes (K8S)
http://kubernetes.io/docs/getting-started-guides/#cloud

Cloud Foundry
http://www.slideshare.net/cdavisafc/cloud-foundry-technical-overview

Apache Mesos – a “Cloud Operating System”
http://www.slideshare.net/Docker/building-web-scale-apps-with-docker-and-mesos/30
• Enterprises have to manage different clusters with different technologies
• Based on containers (but no specific technology, e.g. you can use Docker and rkt)

“The basic resource for CaaS is a container, rather than a virtual machine
(VM) or a bare metal hardware host system.”
Container-as-a-Service (CaaS)
http://searchcloudcomputing.techtarget.com/definition/Containers-as-a-Service-CaaS

Serverless Computing
• Bring a function (not an entire application) up for one single request.
• No cluster or server instance management.
• Small microservice-style functions running for a few (milli)seconds or at latest a few minutes.
• 100% utilization (!!!)
“Sponsored by Red Hat / JBoss"

#7
Be cloud platform agnostic.
The (container) world changes fast!

A
P
I
M
A
N
A
G
E
M
E
N
T
From Containers to a Cloud-Native Platform
Business
Service A1
Java
CRM ERM Host ...
Business
Service A2
Python
Integration
Service A3
Middleware
Business
Service B1
Java
Business
Service B3
Python
Business
Service B2
Go
Integration
Service B4
Middleware
API
API
Cloud-Native
On Premise
Public Cloud
Container(s) Container(s) Container(s)
Cloud-Native Platform

#8
Containers are a lower level technology.
Only the infrastructure provider should care,
but not the application developer!

DevOps Elements – Culture and Technology!
Process
Tools
Automation
Culture
Continuous Integration/
Continuous Development
APIs
MicroservicesFrequent releases
Collaboration

#9
Automation (CI / CD / DevOps) and the related
cultural change are key for success.
Especially for Cloud-Native Microservices!

Microservices,
Cloud, Container,
PaaS, APIs,
Coding, Visual Dev, …
Show me some
cloud native examples!

• Open Source
• Runs on OpenShift PaaS (which is based on Kubernetes)
• Also available as iPaaS
• JBoss Fuse (based on Apache Camel and JBoss A-MQ)
• For Integration Specialists
• Focus on writing source code
JBoss Middleware Services
https://www.openshift.com/container-platform/middleware-services.html

JBoss Example: Apache Camel Integration Service
Java DSL
new RouteBuilder() {
public void configure() {
from(”jms:myQueue").loadBalance()
.circuitBreaker(2, 1000L, MyCustomException.class)
.to("mock:result"); }};
XML DSL
<route>
<from uri=“jms:myQueue"/>
<loadBalance>
<circuitBreaker threshold="2" halfOpenAfter="1000">
<exception>MyCustomException</exception>
</circuitBreaker>
<to uri="mock:result"/>
</loadBalance>
</route>

WSO2
http://wso2.com/cloud/paas/
• Open Source
• Runs on different cloud platforms
• Also available as iPaaS
• WSO2 Products (like ESB or CEP) containerized for cloud offerings
• WSO2 Microservices Framework for Java
• For Integration Specialists
• Focus on writing source code and configuration

TIBCO
• Runs on various cloud platforms (TIBCO BusinessWorks Container Edition)
• Native integration with 3rd party frameworks like Consul or Hystrix
• Also available as iPaaS (TIBCO Cloud Integration)
• Focus on visual coding and productivity
• Powerful IDE (Visual Coding) + Web user interface
• For Integration Specialists and Citizen Integrators

#10
A cloud native architecture
leverages various programming languages,
open source frameworks and middleware!

Develop Deploy
Commit
Build
Config
Demo Setup

Live Demo
Cloud-Native Middleware Development with
• Pivotal Cloud Foundry
• Spring Cloud Config
• Docker
• Kubernetes
• Consul
• Hystrix
• TIBCO BusinessWorks Container Edition
• TIBCO Mashery
• Papertrail

• A cloud-native architecture enables flexible and agile development
• Only vendor- and platform-agnostic architectures are future-safe
• Various languages, open source frameworks and middleware complement each other
Key Takeaways

Questions? Please contact me!
Kai Wähner
Technology Evangelist
kontakt@kai-waehner.de
@KaiWaehner
www.kai-waehner.de
LinkedIn

Case Study: How to move from a Monolith to Cloud, Containers and Microservices

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Similar a Case Study: How to move from a Monolith to Cloud, Containers and Microservices

Similar a Case Study: How to move from a Monolith to Cloud, Containers and Microservices (20)

Más de Kai Wähner

Más de Kai Wähner (20)

Último

Último (20)

Case Study: How to move from a Monolith to Cloud, Containers and Microservices