It's no mystery that currently there is a lot of hype around microservices. You can love them, you can hate them but you can't ignore them. In this presentation I want to tell you my experience from working with microservices architecture for over 2 years now. I will focus mainly on the challenges that needs to be inevitably faced and overcame. As developers, as operations, and also as a whole company. Things that I will touch include distributed systems, more distributed systems and shitload of things that come after microservices you wouldn't expect.

1. the hidden costs of the
microservices architecture
by mirosław nagaś

2. presentation goal
— Simon Brown
“If you can't build a monolith,
what makes you think
microservices are the answer?”

3. microservices 101

4. developed independently by different teams
technology agnostic
loosely coupled
small, easy to replace
microservices 101

6. “There's just no getting around it:
you're building a distributed system”
— Mark Cavage, ACM Queue
¯_( )_/¯
1
microservices 101

7. distributed system
is a
complexity booster
understand
design
build
operate
#12factorapp
#reactivemanifesto

10. eg. fallacies of
distributed computing
the network is reliable
latency is zero
bandwidth is infinite
transport cost is zero
distributed system
introduces
steep learning
curve

11. effects of the fallacies deadly impact communication
communication

12. microservices communicate a LOT
(a)synchronous
communication

13. you will need several
distributed systems
to operate, manage
and monitor your
distributed system
2
microservices 101

14. distributed systems

15. everything-as-a-service
distributed systems

17. shitload of
good things
3
microservices 101

18. release early, release often
SoT
similarity to
IoT
intentional

19. continuous integration
automated tests
continuous delivery
continuous deployment
SoT

20. SoT

21. canary deployments
circuit breakers
central logging
immutable infrastructure
chaos monkey
SoT

22. IaaS
PaaS
365 days of
uptime
is so yesterday…
SoT

23. 4
organisational

24. Image credit: http://martinfowler.com/bliki/MicroservicePrerequisites.html

25. Mr.
Handyman Ops
.org shift
Image credit: http://www.homesenergy.co.uk/

26. DevOps
.org shift

27. collaborative
software development
Image credit: http://martinfowler.com/bliki/DevOpsCulture.html
DevOps

28. NoOps
.org shift

29. it’s not about
elimination of ops people
NoOps

30. it’s about
decentralized operations
NoOps

31. it’s about
full automation for all critical
development and releases processes
NoOps

32. it’s about
scalable, elastic, fault tolerant and
high available systems and infrastructure
NoOps

33. it’s about
products, not projects
.org shift

34. Thank you
@miroslawnagas
lab.getbase.com