Embracy legacy

An internal talk to the Uniplaces team about architecture

Transcript

1. Embrace legacy September 28, Uniplaces Miguel Loureiro
2. The engineering conundrum
3. Software development done by pr0s Start writing from scratch
4. Software development done by pr0s Phase 1 Start writing from scratch
5. Software development done by pr0s Phase 1 Start writing from scratch Phase 2 Launch the product
6. Software development done by pr0s Phase 1 Start writing from scratch Phase 2 Launch the product Phase 3 Architecture doesn’t scale A new framework came out Whatever nonsense happened
7. Software development done by pr0s Phase 1 Start writing from scratch Phase 2 Launch the product Phase 3 Architecture doesn’t scale A new framework came out Whatever nonsense happened Phase 4 Admit it failed miserably and go back to phase 1
8. But, and if there’s no rewrite?
9. But, and if there’s no rewrite? “Legacy here”
10. But, and if there’s no rewrite? “Legacy here” “Legacy there”
11. But, and if there’s no rewrite? “Legacy here” “Legacy there” “Not my fault, legacy”
12. But, and if there’s no rewrite? “Legacy here” “Legacy there” “Oh look, legacy!” “Not my fault, legacy”
13. But, and if there’s no rewrite? “Legacy here” “Legacy there” “Oh look, legacy!” “Not my fault, legacy” “Legacy shit...”
14. But, and if there’s no rewrite? “Legacy here” “Legacy there” “Oh look, legacy!” “Not my fault, legacy” “Legacy shit...” “LEGA“Legac y there” CY” “Legacy there” “Legacy there”
15. Sad truth of the software development industry
16. Legacy = sh#t :(
17. Project objective: Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do
18. Benfica’s legacy Think about this
19. Benfica’s legacy Think about this Every year Benfica changes players
20. Benfica’s legacy Think about this Every year Benfica changes players Every once a while Benfica changes administration
21. Benfica’s legacy Think about this Every year Benfica changes players Every once a while Benfica changes administration Benfica has built a new Stadium
22. Benfica’s legacy Think about this Every year Benfica changes players Every once a while Benfica changes administration Benfica built a new Stadium Benfica is constantly changing
23. Software should leave a legacy
24. How?
25. How? MICROSERVICES
26. Definition Something that tackles one problem independently, in total isolation. 25 35
27. The roots LESSONS - “Divide and conquer” 25 35
28. The roots LESSONS - “Divide and conquer” - “Break problems into smaller problems” 25 35
29. The roots LESSONS - “Divide and conquer” - “Break problems into smaller problems” - “Separation of Concerns” 25 35
30. The roots LESSONS - “Divide and conquer” - “Break problems into smaller problems” - “Separation of Concerns” 25 35 SCOPES - Problem solving
31. The roots LESSONS - “Divide and conquer” - “Break problems into smaller problems” - “Separation of Concerns” 25 35 SCOPES - Problem solving - Procedural programming
32. The roots LESSONS - “Divide and conquer” - “Break problems into smaller problems” - “Separation of Concerns” 25 35 SCOPES - Problem solving - Procedural programming - OOP
33. The roots LESSONS - “Divide and conquer” - “Break problems into smaller problems” - “Separation of Concerns” 25 35 SCOPES - Problem solving - Procedural programming - OOP - MVC
34. The roots LESSONS - “Divide and conquer” - “Break problems into smaller problems” - “Separation of Concerns” 25 35 SCOPES - Problem solving - Procedural programming - OOP - MVC - DDD
35. Every single approach on software development tries to split problems into smaller problems and to separate concerns.
36. “It makes perfect sense that when growing the scope to architecture / infrastructure we see the rise of solutions using the same basic lessons. Microservices didn’t emerge from nothing, they’re a natural architectural evolution from what we’ve been learning.”
37. “It makes perfect sense that when growing the scope to architecture / infrastructure we see the rise of solutions using the same basic lessons. Microservices didn’t emerge from nothing, they’re a natural architectural evolution from what we’ve been learning.”
38. SO WHAT?
39. SO WHAT? What’s our motivation?
40. History 25 35 CORE 5 NINJAS
41. History 25 35 CORE :D ADMIN 5 NINJAS
42. History 25 35 CORE :D ADMIN OPS 5 NINJAS
43. History 25 35 CORE :D ADMIN OPS SHARED LIBRARY (GREAT! ) 5 NINJAS
44. History 25 35 CORE :| SPA PHOTO ADMIN AP OPS SHARED LIBRARY ( OK! ) 9 NINJAS
45. History 25 35 CORE SPA PHOTO ADMIN AP OPS ROOT OF ALL EVIL! 20+ NINJAS
46. History 25 35 SPA PHOTO ADMIN AP OPS ROOT OF ALL EVIL! 20+ NINJAS COUPLED ARCHITECTURE CORE
47. Problems - Team scalability
48. Problems - Team scalability - Missing bounded context (back to this later)
49. Problems - Team scalability - Missing bounded context (back to this later) - Dependency hell
50. Problems - Team scalability - Missing bounded context (back to this later) - Dependency hell - Granular scalability
51. Problems - Team scalability - Missing bounded context (back to this later) - Dependency hell - Granular scalability - Missing isolated development
52. Problems - Team scalability - Missing bounded context (back to this later) - Dependency hell - Granular scalability - Missing isolated development - Slowdown release pipeline
53. But with shared libraries I’m following DRY :/
54. “My general rule of thumb: don’t violate DRY within a microservice, but be relaxed about violating DRY across all services. The evils of too much coupling between services are far worse than the problems caused by code duplication”
55. “My general rule of thumb: don’t violate DRY within a microservice, but be relaxed about violating DRY across all services. The evils of too much coupling between services are far worse than the problems caused by code duplication”
56. Now, how are we doing this?
57. Problems - Organizational scalability - Missing bounded context (back to this later)
58. We have bounded context with Domain Driven Design We just don’t have separate delivery pipelines for each one
59. Are we going crazy on this?
60. On going 25 35 CORE (Monolith) SPA PHOTO ADMIN AP OPS ROOT OF ALL EVIL! 20+ NINJAS Auth Rents calculator Pricing calculator Search API Search JOBS
61. Orchestration or Choreography ?
62. Orchestration or Choreography ? Orchestration 25 35 Choreography
63. We start with choreography
64. Message consumers are being written in Golang
65. Cluster management
66. Fully automated releases 1. Merge to master
67. Fully automated releases 1. Merge to master 2. Circle CI BUILDS docker image, TAGS it and PUSHES to a private docker registry.
68. Fully automated releases 1. Merge to master 2. Circle CI BUILDS docker image, TAGS it and PUSHES to private docker registry. 3. Update service with the new task definition
69. The vision 25 35 SPA PHOTO ADMIN AP OPS 500+ NINJAS Auth Rents calculator Pricing calculator Search API Search JOBS Offers Properties Cities Neighborhoods Communication A B D C D 10+ LANGUAGES MOBILE APP B MOBILE APP A MOBILE APP C MOBILE APP D
70. Canary releases
71. The right tool for the right job
72. Business will never hear about rewriting the product again
73. Leave your legacy