Scaling with Microservices DevOps Turkey 2021

1. DevOps Turkey’2021
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. Ref: https://medium.com/@ddarie/the-strangler-fig-migration-pattern-2e20a7350511

11. What is Strangler-Fig?

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

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

14. Problem?

15. Why we need scaling?

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

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

18. Bottlenecks?

19. Solution?

20. How you will scale?

21. How you will scale?

22. How you will scale?

23. Scale Cube

24. Why not invest on Scale Cube?

26. Bottlenecks?

27. 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”

28. Is your architecture
ready to be
decoupled?

29. Is your
organisation
ready to be
decoupled?

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

31. Are Microservices the ultimate
solution to scaling?

32. Depends...

33. Microservices is not an
architecture!

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

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

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

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

38. CAP Theorem
Consistency Availability
Partition
Tolerance
N/A
CA
CP AP

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

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

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

42. Benefits of Microservices

43. Challenges of Microservices
● Lack of Governance
● Service Communication
● Data staleness
● Service / Resource Discovery
● Distributed Transaction

44. 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

45. Thank you!
Derya SEZEN a.k.a Dorian
Techie @kloia
@derya_sezen
career@kloia.com