Presented at Sydney Software Crafters - https://www.meetup.com/Software-Crafters-Sydney/events/245851973/?comment_table_id=255462291&comment_table_name=reply

1. My journey through microservices so far…
Phil Calçado
h:p://philcalcado.com
@pcalcado

3. Zeroth IteraBon:
ThoughtWorks

4. What the client’s architect oGen wanted
WebSphere
Monolith.ear

5. Tomcat
TomcatTomcat
TomcatTomcat
TomcatTomcat
Tomcat
What we wanted to build
.war .war .war .war
.war .war .war .war

6. What we oGen built
.jar .jar .jar .jar
.jar .jar .jar
WebSphere
.jar

7. First IteraBon:
SoundCloud

8. Small European company fighBng the
giants of the music industry.

9. "We used to deliver features at light-speed,
growing the team has slowed us down!"

10. Old value chain

11. Amongst other changes

12. New value chain

13. h:p://philcalcado.com/2015/09/08/how_we_ended_up_with_microservices.html

14. Second IteraBon:
DigitalOcean

15. Small New York startup fighBng the giants
of cloud compuBng.

16. "We know exactly what we need to deliver.
All we need is to hire more people."

17. No new product in years.

18. ! "
#
Control Panel Group Internal Tools Group
Back-end Group

19. Control Panel Microlith Internal Tools Microlith
Back-end Microlith

20. Amongst other changes

22. In Conclusion

23. Engineering is
the bo:leneck
Legal/Product is
the bo:leneck

24. Engineering is
the bo:leneck
Legal/Product is
the bo:leneck

25. Fin.

26. …or is it?

27. server
client

28. server
client
🔥🔥 🔥

30. 🔥
wait
☺ 😰
🔥 🔥
wait
☺ 😰
🔥
☺
☺
☺
☺
☺
☺
☺
☺

31. server
client client client client client client

32. 🔥
wait
☺ 😰
🔥 🔥
wait
☺ 😰
🔥
☺
☺
☺
☺
☺
☺
☺
☺

33. 🔥
wait
☺ 😰
🔥 🔥
☺
wait
😰 ☺
🔥 🔥
wait
😰 ☺
🔥 🔥
wait
😰 ☺
🔥 🔥
…

34. 🔥
🗑

35. "I know, let’s have all circuit
breakers share state”

36. "I know, let’s have all circuit
breakers share state”
Answer to the question “how did my
application ended up importing a
Zookeeper library again?"

37. server
client
🔥🔥 🔥
server server serverserver
🔥🔥 🔥💩
🤔
Which instance should we talk to?
☺

38. DNS be like…
*

39. Circuit breakers
Timeouts
This is your code on microservices
Biz Logic
Timeouts
Telemetry
…
Distributed state
Client-side
Service Discovery

40. The dirty li:le secret
no microservices
evangelist tell you:

41. Google/SoundCloud/Twi:er/
Nedlix/Facebook/etc. have more
engineers working on their internal
tooling than the total number of
employees at your workplace.

42. i.e. microservices
are complicated af

43. Third IteraBon:
Buoyant

44. Circuit breakers
Timeouts
Biz Logic
Timeouts
Telemetry
RPC code
Distributed state
Client-side
Service Discovery
SDK
Historically, this complicaBon leaks into your service

45. Sidecars to the rescue
Circuit breakers
Timeouts
Biz Logic
Timeouts
Telemetry
RPC code
Distributed state
Client-side
Service Discovery
SCARY OUTSIDE
WORLD

46. Sidecars to the rescue
Circuit breakers
Timeouts
Biz Logic
Timeouts
Telemetry
RPC code
Distributed state
Client-side
Service Discovery
SCARY OUTSIDE
WORLDSidecar

47. Sidecars form their own network

48. ApplicaBon
Transport
Internet
Network
Circuit breakers
Telemetry
RPC code
Distributed state
Client-side
Service Discovery
}TCP/IP
}?
One way to think about it

50. Two examples of Service Mesh
• All-in-one
• ProducBon ready
• Next-generaBon
• For Kubernetes

51. It’s not that these pa:erns aren’t
used anymore, it’s just that the
dumb work moved down the stack.

52. New, optmised, protocols are quite opaque
(e.g. gRPC and friends)
Works be:er with
metadata-rich protocols

53. It makes it even harder to fully replicate
producBon earlier in the development cycle
Coupled to the pladorm

54. Not everything will be part of the mesh,
i.e. the network sBll isn’t homogeneous
Leaky abstracBon

55. Q&A