The document discusses the evolution of containerization and microservices, emphasizing the dominance of Docker and Kubernetes and the maturity of cloud services. It highlights the importance of agile practices, the role of APIs, and the growing complexity associated with microservices architecture. The text also points out challenges in aligning processes with business needs and the necessity of pragmatic solutions for success.

1. 2020 & Beyond…

2.  Dominated by Docker
 But this space is getting crowded with new
offerings

3. Kubernetes becoming the de-facto standard

4.  Cloud containerization service offerings
continues to mature
(GKE,AKS,Amazon ECS/EKS,IBM Cloud Kubernetes
Service,...)

5.  Container Agnostic
 Serverless
 Governed Polyglot

6.  Getting rich & mature
 Covering end-to-end lifecycle
Management,Runtime,Monitoring,Networking,
Registry,Discovery…

7.  Patterns driving the design
 Very well established set of patterns & anti-
patterns

8.  Agile (in some form) is the only way forward…
 API becomes the primary citizen
GraphQL & REST set to fight it out…
Both would stay around for long!

9.  Vast set of tools to choose from
 Increasingly leveraged to derive the benefits of
microservices strategy

10.  Recognized as the most important factor for
success
 Need not be perfect… Having a pragmatic
process that works a must!!!
Can you define a processes that aligns your business,
development & operations while preserving your
organization culture?

11.  Continues to be a challenge…
 OCI – Trying to put the basics in place
Innovation continues to be driven more by
competition and need than by the standards (at this
point in time)…

12.  Hype has subsided…
 Increasing upfront investment to validate if
microservices is the right strategy
Increasing instances of selective microservice
adoption… Microservices architecture vs.also have
microservices in the architecture…

13. Speed? Rapid innovation? Handle growth/expansion?
Selectively scalable? Business alignment? Flexibility?
Productivity? Resilient? Agile enablement? Team
empowerment?...
Be clear on the why part!!!

14.  It is not a simplification
With more moving parts,variety of technologies &
multiplied remote integrations,the overall
complexity increases and the micro-services system
in general is more prone to errors

15. Feedback and suggestions welcome.Please write to
ashokkumar.ta@gmail.com