This document summarizes a presentation about scaling with microservices. It discusses that microservices are not just Docker/Kubernetes and are not just smaller services, but rather represent a new data model. It also discusses patterns for splitting a monolith architecture into microservices using the strangler fig pattern. The presentation addresses common problems organizations face with scaling and bottlenecks. It discusses how microservices can help with scaling but also come with tradeoffs around consistency versus availability that require business input. The presentation recommends steps organizations should take prior to adopting microservices like understanding domain models and consistency requirements.

1. Baku DevOpsDays AZ’2020
Scaling with Microservices
Derya SEZEN a.k.a Dorian
Consultant @kloia (CNCF Member)
DevOpsDays Istanbul Organizer
@derya_sezen

3. Microservices is not Docker/Kubernetes

4. Microservices is not just smaller services

5. Ref: https://www.xenonstack.com/insights/service-oriented-architecture-vs-microservices/

6. Ref: https://www.browserlondon.com/blog/2019/07/01/do-you-need-microservices/

7. Microservices is a new data model

8. What if you have a Monolith?

9. Splitting the Monolith
with Strangler-Fig Pattern

10. What is Strangler-Fig?

11. Ref: https://medium.com/@ddarie/the-strangler-fig-migration-pattern-2e20a7350511

12. Ref: https://www.michielrook.nl/2016/11/strangler-pattern-practice/
/serviceA

13. Problem?

14. Why we need scaling?

15. Is your business/data/load is growing?

16. “Global mobile users to exceed 5.5B by 2022”
-- Forrester

17. Bottlenecks?

18. Solution?

19. How you will scale?

20. How you will scale?

21. How you will scale?

22. Scale Cube

23. Why not invest on Scale Cube?

25. Bottlenecks?

26. Conway’s Law:
“Any organization that designs a system will inevitably
produce a design whose structure is a copy of the
organization's communication structure”

27. Is your architecture
ready to be
decoupled?

28. Is your
organisation
ready to be
decoupled?

29. Is your business
convinced to
invest on that
non-functional
change?

30. Are Microservices the ultimate
solution to scaling?

31. Depends...

32. Microservices is not an
architecture!

33. Consistency
Stock = 1
Stock = 1
Replication
Checkout
Product Page

34. Inconsistency
Stock = 0
Stock = 1
Replication
Checkout
Product Page

35. Inconsistency
Stock = 0
Stock = 1
Broken link!
Checkout
Product Page

36. Choose Availability or Consistency?
A or C?
Availability Consistency
Continue with
Inconsistency
Return Error to User

37. “Availability over consistency is not a
technical choice, it is a business choice.”
-- Anonymous

38. Ask your business?
Which one they prefer?
1- The website goes down
2- Website shows products with Stock=0

39. Eventual Consistency examples?
Twitter likes/timelines
Facebook news
Amazon Cart/Payment

40. Benefits of Microservices

41. Prior to moving to Microservices
● Consider your organizational structure
● Know your domain-model (i.e. Apply Event Storming)
● Go over the consistency requirements with business
● Increase the maturity of software teams
● Adapt a DevOps Culture

42. Thank you!
Derya SEZEN a.k.a Dorian
Consultant @kloia
@derya_sezen