Growing tech at a startup @ Pixels.camp 2016

Transcript

1. Growing tech at a startup October 7, pixels.camp Miguel Loureiro
2. berlinballs.com
3. Start writing from scratch
4. Benfica’s legacy Think about this
5. CTO College mate that knows a bazillion languages
9. 1 year after
10. 1 year after Excellent growth
11. 1 year after Excellent growth Funding
12. 1 year after More engineers Excellent growth Funding
13. 1 year after More engineers Excellent growth Funding Happy fat grandmas
14. Life goes well
15. Life goes well, except for the tech debt
16. CTO College mate that knows a bazillion languages
17. Rewrite everything
18. Integrate
19. Integrate “Legacy here”
20. Integrate “Legacy here” “Legacy there”
21. Integrate “Legacy here” “Legacy there” “Not my fault, legacy”
22. Integrate “Legacy here” “Legacy there” “Not my fault, legacy” “Oh look, legacy!”
23. Integrate “Legacy here” “Legacy there” “Not my fault, legacy” “Oh look, legacy!” “Legacy there” “LEGA“Legac y there” CY” “Legacy shit...” “Legacy there”
24. Think about this
25. Exercise
26. Pre production 25 35 API 5 DEVS 1 REPO 2 ENV 1 DB 0 DEPLOYS
27. Pre production 25 35 API ADMIN 5 DEVS 2 REPO 2 ENV 1 DB 0 DEPLOYS
28. Pre production 25 35 API ADMIN OPS 5 DEVS 3 REPO 2 ENV 1 DB 0 DEPLOYS
29. Pre production 25 35 API ADMIN OPS 5 DEVS 3 REPO 2 ENV 1 DB 0 DEPLOYS Teams attached to projects
30. Pre production 25 35 API ADMIN OPS SHARED LIBRARY (GREAT! ) 5 DEVS 4 REPO 2 ENV 1 DB 0 DEPLOYS
31. Staging 25 35 API ADMIN OPS SHARED LIBRARY (GREAT! ) 5 DEVS 4 REPO 3 ENV 2 DB 8 DEPLOYS
32. Production and Staging 25 35 API DEMAND AUX ADMIN SUPPLY OPS SHARED LIBRARY ( HMMMM... ) 13 DEVS 9 REPO 4 ENV 2 DB 1 SE 44 DEPLOYS JOBS 2 JOBS 1
33. Production and Staging 25 35 API DEMAND AUX ADMIN SUPPLY OPS SHARED LIBRARY ( HMMMM... ) 13 DEVS 9 REPO 4 ENV 3 DB 1 SE 46 DEPLOYS JOBS 2 JOBS 1 Reporting
34. Production and Staging 25 35 API DEM AND AUX ADMIN SU PP LY OPS ROOT OF ALL EVIL! 20 DEVS 13 REPO 4 ENV 3 DB 1 SE 80+ DEPL.. Reporting JOBS 2 JOBS 1 AUX app SUPPLY app Mobile API (read proxy)
35. Production and Staging 25 35 API DEM AND AUX ADMIN SU PP LY OPS ROOT OF ALL EVIL! 20 DEVS 13 REPO 4 ENV 3 DB 1 SE 80+ DEPL.. Reporting JOBS 2 JOBS 1 AUX app SUPPLY app Mobile API (read proxy) Leaked domain logic
36. Production and Staging 25 35 API DEM AND AUX ADMIN SU PP LY OPS ROOT OF ALL EVIL! 20 DEVS 13 REPO 4 ENV 3 DB 1 SE 80+ DEPL.. Reporting JOBS 2 JOBS 1 AUX app SUPPLY app Mobile API (read proxy) Leaked domain logic Doesn’t scale anymore
37. Production and Staging 25 35 API DEM AND AUX ADMIN SU PP LY OPS ROOT OF ALL EVIL! 20 DEVS 13 REPO 4 ENV 3 DB 1 SE 80+ DEPL.. Reporting JOBS 2 JOBS 1 AUX app SUPPLY app Mobile API (read proxy) Leaked domain logic Doesn’t scale anymore COUPLED ARCHITECTURE
38. Team scalability
39. Increasingly slower release cycle
40. Bored team
41. How are you fixing this?
42. Production and Staging 25 35 API DEM AND AUX ADMIN SU PP LY OPS ROOT OF ALL EVIL! 20 DEVS 12 REPO 4 ENV 3 DB 1 SE 80+ DEPL.. Reporting JOBS 2 JOBS 1 AUX app SUPPLY app Mobile API (read proxy)
43. But with shared libraries I’m following DRY :/
44. “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”
45. Production and Staging 25 35 API DEM AND AUX ADMIN SU PP LY OPS ROOT OF ALL EVIL! 20 DEVS 12 REPO 4 ENV 3 DB 1 SE 80+ DEPL.. Reporting JOBS 2 JOBS 1 AUX app SUPPLY app Mobile API (read proxy) SPLIT THIS
46. REFACTORING THE PROJECT THAT HAS THE WHOLE BUSINESS LOGIC?!?!?!??
47. We’ll use the bounded context provided by Domain Driven Design We just need to have separate delivery pipelines for each one (directory)
48. Start with small use cases
49. Production and Staging 25 35 API DEM AND AUX ADMIN SU PP LY OPS ROOT OF ALL EVIL! 20 DEVS 17 REPO 4 ENV 3 DB 1 SE 120+ DEPL.. Reporting JOBS 2 JOBS 1 AUX app SUPPLY app Mobile API (read proxy) Auth Pricing calculator Search API Search Jobs
50. Orchestration or Choreography ?
51. Orchestration or Choreography ? Orchestration 25 35 Choreography
52. Start with choreography
53. Message consumers are being written in Golang
54. Cluster management
55. Fully automated releases 1. Merge to master
56. Fully automated releases 1. Merge to master 2. Circle CI BUILDS docker image, TAGS it and PUSHES to a private docker registry.
57. Fully automated releases 1. Merge to master 2. Circle CI BUILDS docker image, TAGS it and PUSHES to a private docker registry. 3. Update service with the new task definition
58. Production and Staging 25 35 API DEM AND AUX ADMIN SU PP LY OPS ROOT OF ALL EVIL! 20 DEVS 17 REPO 4 ENV 3 DB 1 SE 120+ DEPL.. Reporting JOBS 2 JOBS 1 AUX app SUPPLY app Mobile API (read proxy) Auth Pricing calculator Search API Search Jobs
59. Production and Staging 25 35 DEM AND AUX ADMIN SU PP LY OPS 20+ DEVS 40+ REPO 4 ENV 3 DB 1 SE 200+ DEPL.. Reporting JOBS 2 JOBS 1 AUX app SUPPLY app Mobile API (read proxy) Auth Pricing calculator Search API Search Jobs Offers Properties Communication ... Considering mono repo
60. Team organization Squad A1 Squad B1 Squad C1 Squad C2 Squad A2 Squad B2 Squad D1 Squad D2 25 35 DEM AND AUX ADMIN SU PP LY OPS Reporting JOBS 2 JOBS 1 AUX app SUPPLY app Mobile API (read proxy) Auth Pricing calculator Search API Search Jobs Offers Properties Communication ... Squad Small 3 devs Autonomous Motivated
61. You’ve just built @ Pixels Camp 2016
62. 1. Define the quality standards
63. 80/20 rule
64. 2. Pick the right approach
65. Code primary focus on business Bounded Context Ubiquitous Language
66. Languages, frameworks, databases...
67. Languages, frameworks, databases... ARE JUST DETAILS
68. 3. DevOps culture
69. Mindset
70. History 25 35 CORE 3 DEVELOPERS 1 LANGUAGES 1 ENVIRONMENT
71. Create your environments
72. Invest in your release pipelines
73. Release a lot
74. Growing is not about picking technologies
75. Questions? @mlimaloureiro