Transition from Monolithic Solutions to MicroSevices (BIG to SMALL)

Transition from Monolithic Solutions
to MicroSevices
(BIG to SMALL)

Questions

Scale

Sustainability

Maintainability

What are the measures
of success?

Why small over big?
What problems are we attempting to solve?

How do we go from big to small
in a smooth and easy fashion?

Deliver value faster

Accelerate the pace of change

Each service is self serving encapsulating
a business capability

Organize - Autonomous Teams
responsible for one / multiple
services

Size of the service is not important
(Microservices is a label not the description)

Increase speed of experimentation

Business service offerings
have independent lifecycles

Business and IT ecosystem enables
swift growth and scale
of operational changes
(Business OPS/ IT OPS)

Setup Basic Monitoring & Automated Response Mechanism
(Services, Infrastructure, Security)

Develop a Rapid Application Deployment Strategy
Pivot in Deployment Methodology

Go to the Cloud
Cloud Computing

Setup DevOps

Implement Automated Deployment Framework

Implement Container Orchestration
(deployment infrastructure abstraction)
(Continuous Integration/Delivery - GoCD - Kubernetes)

Create a Standard - Service Mesh
(Standard approach for API/ESB)
https://www.thoughtworks.com/radar/techniques/service-mesh

Decouple edge services first
Decouple capability not code
(Minimize dependency to monolith)
(Decouple interdependence to monolith)

Continuous Delivery
Continuous Integration

Modular Application Design
Application changes implemented with minimal
or no system downtime

Lower cost
to maintain, implement, rollback
(Applications, Infrastructure, Change Management, Risk)
(KPIs)

DevOps

Organize - Feature Teams

Change in Governance Model
(Open Source Governance Model)
https://en.wikipedia.org/wiki/Open-source_governance

Lower cost to maintain, implement,
impact to system

Develop an infrastructure strategy that
can achieve Microservices solutions