Current tech marketing aims at making you fall in love with microservices. But do you know their benefits and their requirements? What about their feasibility?

1. THE DARK SIDE
OF MICRO-
SERVICES
@NICOLAS_FRANKEL

2. #microservices
ME, MYSELF AND I
@nicolas_frankel
2
 Developer/Software -
/Solution Architect
• Java
• As consultant

3. #microservices
MICRO-SERVICES ON PAPER
3
@nicolas_frankel

4. #microservices
QUOTE OF THE DAY
@nicolas_frankel
4
“[…] if people can't build
monoliths properly,
microservices won't help”
- Simon Brown
https://twitter.com/simonbrown/status/573072777147777024
https://genehughson.wordpress.com/2015/03/08/microservice-architectures-arent-for-everyone/

5. #microservices
QUOTE OF THE DAY
@nicolas_frankel
5
“I see you have a poorly
structured monolith. Would
you like me to convert it into a
poorly structured set of
microservices?”
- Architect Clippy
https://twitter.com/architectclippy/status/570025079825764352
https://genehughson.wordpress.com/2015/03/08/microservice-architectures-arent-for-everyone/

6. #microservices
MICRO-SERVICES IN REAL LIFE
6
@nicolas_frankel

7. #microservices
SUMMARY
What are micro-services?
What benefits to expect?
What requirements?
What’s in it for you now?
7
@nicolas_frankel

8. #microservices
A TENTATIVE
DEFINITION
THE DARK SIDE OF MICRO-SERVICES
8
@nicolas_frankel

9. #microservices
THE MONOLITH
“A monolithic application
puts all its functionality into a
single process…”
http://martinfowler.com/articles/microservices.html
9
@nicolas_frankel

10. #microservices
SCALING A MONOLITH
“… and scales by replicating
the monolith on different
servers”
10
@nicolas_frankel

11. #microservices
ASSUMPTION
All functionalities of your
application have the same
load
• Really?
11
@nicolas_frankel

12. #microservices
EXAMPLE: E-COMMERCE SHOP
Catalog
Cart
Login
Payment
etc.
12
@nicolas_frankel

13. #microservices
MICRO-SERVICES
“A microservices
architecture puts each
element of functionality into
a separate service…”
13
@nicolas_frankel

14. #microservices
SCALING MICRO-SERVICES
“… and scales by
distributing these services
across servers, scaling as
needed”
14
@nicolas_frankel

15. #microservices
SINGLE RESPONSIBILITY PRINCIPLE
 Component-based
 Wrapping a single business
capability
• Fine-grained
 Decoupled from one
another
 Communicating via simple
channels
15
@nicolas_frankel

16. #microservices
BENEFITS
THE DARK SIDE OF MICRO-SERVICES
16
@nicolas_frankel

17. #microservices
DIFFERENTIAL SCALING
Optimizing resources
17
@nicolas_frankel

18. #microservices
DECOUPLED LIFECYCLES
Enable continuous delivery
• No more release trains!
18
@nicolas_frankel

19. #microservices
CONTINUOUS/EVOLUTIONARY DESIGN
No necessary fixed upfront
design
• Allows for continuous changes
19
@nicolas_frankel

20. #microservices
POLYGLOT PERSISTENCE
Choose the best persistence
tier for the job
20
@nicolas_frankel

21. #microservices
POLYGLOT
Choose the best language
for the job
21
@nicolas_frankel

22. #microservices
REQUIREMENTS
THE DARK SIDE OF MICRO-SERVICES
22
@nicolas_frankel

23. #microservices
INFRASTRUCTURE AUTOMATION
To deliver continuously
23
@nicolas_frankel

24. #microservices
FORMALIZED DOCUMENTATION
To help service users
24
@nicolas_frankel

25. #microservices
MONITORING
Cross-components
25
@nicolas_frankel

26. #microservices
CORE ISSUES
THE DARK SIDE OF MICRO-SERVICES
27
@nicolas_frankel

27. #microservices
28
@nicolas_frankel

28. #microservices
THE NETWORK!
From a simple API call to a
network call…
29
@nicolas_frankel

29. #microservices
FALLACIES OF DISTRIBUTED
COMPUTING
1. The network is reliable.
2. Latency is zero.
3. Bandwidth is infinite.
4. The network is secure.
5. Topology doesn’t change.
6. There is one administrator.
7. Transport cost is zero.
8. The network is homogeneous.
@nicolas_frankel
30

30. #microservices
NEW PROBLEMS ARISE
Latency
• Asynchronicity
• Performance drop
31
@nicolas_frankel

31. #microservices
NEW PROBLEMS ARISE
Handling failures
• Different handling
• Unavailable service
32
@nicolas_frankel

32. #microservices
NEW PROBLEMS ARISE
Serialization/deserialization
• Performance drop
33
@nicolas_frankel

33. #microservices
STRIKE A BALANCE
Between scalability and
performance
34
@nicolas_frankel

34. #microservices
NOT ONLY TECHNICAL ISSUES
@nicolas_frankel
35

35. #microservices
AGILE?
Trying to do agile
Doing agile
Being agile
36
@nicolas_frankel

36. #microservices
ORGANIZING TEAMS
Limited size
• Fed by 2 pizzas
Autonomous
Self-organizing
37
@nicolas_frankel

37. #microservices
ORGANIZATION AT NETFLIX
@nicolas_frankel
38

38. #microservices
THE BANE OF MIDDLE MANAGEMENT
Most middle managers are
useless
• But they want to keep their jobs
Better suited to
• Small companies
• Rather flat organizations
39
@nicolas_frankel

39. #microservices
THE LIGHT SIDE
THE DARK SIDE OF MICRO-SERVICES
40
@nicolas_frankel

40. #microservices
AND YET…
41
@nicolas_frankel

41. #microservices
THERE ARE MICRO-SERVICES…
… and web-services
• RESTful
42
@nicolas_frankel

42. #microservices
MICRO-SERVICES ENABLERS
@nicolas_frankel
43
Hystrix
Ribbon
Eureka
Feign

43. #microservices
FEATURES
@nicolas_frankel
44
Circuit breaker
• Fail-fast
Fallback
Cache
Collapse
Dashboard
And many more…
https://github.com/Netflix/Hystrix/wiki/How-To-Use

44. #microservices
CIRCUIT-BREAKER
@nicolas_frankel
45

45. #microservices
FALLBACK
@nicolas_frankel
46

46. #microservices
REQUEST
COLLAPSE
@nicolas_frankel
47

47. #microservices
REQUEST
COLLAPSE
@nicolas_frankel
48

48. #microservices
DASHBOARD
@nicolas_frankel
49

49. #microservices
API FLAVORS
@nicolas_frankel
50
Synchronous
Asynchronous
Reactive

50. #microservices
RIBBON
@nicolas_frankel
51
Client-side load-balancer
Pluggable rules

51. #microservices
COMMONS RULES
@nicolas_frankel
52
Round robbin
Availability filtering
Weighted response time
<insert your own there>

52. #microservices
SERVER LIST
@nicolas_frankel
53
Ad hoc
Configuration-based
Discovery enabled
• Through Eureka

53. #microservices
EUREKA
@nicolas_frankel
54
Registry for middle tier load
balancing
• Server
• Client

54. #microservices
FEIGN
@nicolas_frankel
55
Annotation based REST
client

55. #microservices
SPRING CLOUD*
@nicolas_frankel
56

56. #microservices
SUMMARY
THE DARK SIDE OF MICRO-SERVICES
57
@nicolas_frankel

57. #microservices
ADOPT AN ENGINEER MINDSET
@nicolas_frankel
58
Evaluate benefits
Evaluate costs
Evaluate feasibility
• Technical
• Organizational

58. #microservices
Q&A
@nicolas_frankel
59
http://blog.frankel.ch/
@nicolas_frankel
http://frankel.in/