Codemotion 2016

1. Microservicios,
en qué lío me he metido
by
MADRID · NOV 18-19 · 2016
Ernesto Hernández
@ehdez73
Miguel Ortega
@mortegarod

2. MADRID · NOV 18-19 · 2016

3. MADRID · NOV 18-19 · 2016

4. MADRID · NOV 18-19 · 2016
● 7 Countries
● Over 50 carriers
● >300 shipping services
● >500% shipment grow
● >2M shipments/year

5. MADRID · NOV 18-19 · 2016
GIVEN:
The team size, the requirements and the
legacy systems that we had.
WHEN:
We tried to migrate to a microservices
architecture.
THEN:
We found that this approach to
microservices was the one that better
suited to our needs.
Work in progress

6. MADRID · NOV 18-19 · 2016
New Idea
http://transformcustomers.com/category/business-transformation/

7. MADRID · NOV 18-19 · 2016
Our legacy old
Monolith
http://isijisan.blogspot.com.es/2015/03/el-escarabajo-pelotero.html

8. MADRID · NOV 18-19 · 2016
Fast growth

9. MADRID · NOV 18-19 · 2016
Our shiny
and new
Monolith
https://mekubal.wordpress.com/2012/04/03/the-myth-of-monolithic-judaism/
KOKUDO

10. MADRID · NOV 18-19 · 2016
Our Monoliths
KOKUDO

11. MADRID · NOV 18-19 · 2016
Business needs!!! We need an API

12. MADRID · NOV 18-19 · 2016Sometimes you need to clean up

13. MADRID · NOV 18-19 · 2016
● Another monolith
● ESB orchestration
● DB coupling
● Fixed deploy dates
● Something distributed
● More choreography
● Different storages
● Deploy flexibility

14. MADRID · NOV 18-19 · 2016
It seems clear right?
Microservices

15. MADRID · NOV 18-19 · 2016
Not so fast...
2014 2015 2016

16. MADRID · NOV 18-19 · 2016but what the hell is a microservice?
CHALLENGE
ACCEPTED

17. MADRID · NOV 18-19 · 2016
Packlinktechture Phase 1

18. MADRID · NOV 18-19 · 2016
Packlinktechture Phase 1

19. MADRID · NOV 18-19 · 2016
Packlinktechture Phase 2

20. MADRID · NOV 18-19 · 2016
Packlinktechture Phase 2
● ONE DATABASE
● CODE STILL IN MONOLITH
FATAL

21. MADRID · NOV 18-19 · 2016
Packlinktechture Phase 3

22. MADRID · NOV 18-19 · 2016
Packlinktechture Phase 3
● ONE DATABASE
● NO REAL MICROSERVICES
● DEPLOY/CONFIGURATION HELL
ERROR

23. MADRID · NOV 18-19 · 2016
Turn
Around

24. MADRID · NOV 18-19 · 2016
Packlinktechture Phase 4

25. MADRID · NOV 18-19 · 2016
Synchronous
Network call

26. MADRID · NOV 18-19 · 2016
Synchronous
Network call

27. MADRID · NOV 18-19 · 2016
Packlinktechture Phase 4

28. MADRID · NOV 18-19 · 2016
Packlinktechture Phase 4
● SYNCHRONOUS CALLS HELL
● WHERE ARE MY JOINS?
warning

29. MADRID · NOV 18-19 · 2016
Asynchronous
MESSAGE BUS

30. MADRID · NOV 18-19 · 2016
Packlinktechture Phase 5

31. MADRID · NOV 18-19 · 2016
Packlinktechture Phase 5

32. MADRID · NOV 18-19 · 2016
Packlinktechture Phase 5

33. MADRID · NOV 18-19 · 2016
Packlinktechture Phase 5
● SHARED LIBRARY
● NEW MONOLITHS
INFO

34. MADRID · NOV 18-19 · 2016
Packlinktechture Phase 6

35. MADRID · NOV 18-19 · 2016
Packlinktechture Phase 6
● DUDE, WHERE ARE MY LOGS?
DEBUG

36. MADRID · NOV 18-19 · 2016
Correlation id
Network call
{ correlation_id: 123, ... }
{ correlation_id: 123, ... }{ correlation_id: 123, ... }
{ correlation_id: 123, ... }
{ correlation_id: 123, ... }
{ correlation_id: 123, ... }

37. MADRID · NOV 18-19 · 2016
Logging stack

38. MADRID · NOV 18-19 · 2016
Logging stack
TRACE

39. MADRID · NOV 18-19 · 2016
● EVENT SOURCING
● CQRS

40. MADRID · NOV 18-19 · 2016
The Platform

41. MADRID · NOV 18-19 · 2016
Docker Ecosystem FTW
● build once, run everywhere
● easy scaling with docker-compose
● infrastructure scaling with swarm

42. MADRID · NOV 18-19 · 2016
Hashicorp Consul
- Key/Value
- consul-template
- Leader election
- DNS
- Already needed for docker swarm

43. MADRID · NOV 18-19 · 2016
Service discovery

44. MADRID · NOV 18-19 · 2016
How do I develop locally?

45. MADRID · NOV 18-19 · 2016
New old problems
● Onboarding new developers
● Config management
● Debugging
● Data Bootstrapping

46. MADRID · NOV 18-19 · 2016
What do we need?
● Infrastructure Bootstrapping:
○ up and running
○ configuration
● Microservices Bootstrapping:
○ up and running
○ application data

47. MADRID · NOV 18-19 · 2016
How do we solved it?
● Infrastructure Bootstrapping.
○ up and running
○ configuration
● Microservices Bootstrapping:
○ up and running
○ application data

48. MADRID · NOV 18-19 · 2016
How do we solved it?
● Infrastructure Bootstrapping.
○ up and running
○ configuration
● Microservices Bootstrapping:
○ up and running
○ application data

49. MADRID · NOV 18-19 · 2016
Local development

50. MADRID · NOV 18-19 · 2016
Service discovery (review)

51. MADRID · NOV 18-19 · 2016
Service discovery (IDE)

52. MADRID · NOV 18-19 · 2016
Service discovery (remote)

53. MADRID · NOV 18-19 · 2016
Service discovery (all together)

54. MADRID · NOV 18-19 · 2016
Our (helpful) Dev Tools

55. MADRID · NOV 18-19 · 2016
https://slack.com

56. MADRID · NOV 18-19 · 2016
https://newrelic.com

57. MADRID · NOV 18-19 · 2016
Wiggumbot
https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin
http://docs.sonarqube.org/display/PLUG/GitHub+Plugin

58. MADRID · NOV 18-19 · 2016
Hound
https://github.com/etsy/hound
Etsy, Inc.

59. MADRID · NOV 18-19 · 2016
Asciidoctor
http://asciidoctor.org

60. MADRID · NOV 18-19 · 2016
Custom scripts
check-status.sh
compose-upgrade.sh

61. dashboards
checks
channels
metrics
Platform monitoring

62. MADRID · NOV 18-19 · 2016
Was it worth it?

63. MADRID · NOV 18-19 · 2016
# Shipments

64. MADRID · NOV 18-19 · 2016
# Deployments
2 → ~20 per week

65. MADRID · NOV 18-19 · 2016
It seems clear right?
Q&A

66. MADRID · NOV 18-19 · 2016
Thank you

67. MADRID · NOV 18-19 · 2016
WE ARE HIRING