Microservices for Startups: Build to Adapt

The path to a successful startup is never a straight one. Your business needs to be adaptable, and so should your architecture. This session will explore adopting a microservices architecture from the start. Why microservices for a startup? Small and focused services can evolve independently as your business needs change.

https://www.denverstartupweek.org/schedule/3586-microservices-for-startups-build-to-adapt

Transcript

1. MICROSERVICES FOR STARTUPS: BUILD TO ADAPT Travis Nelson September 28, 2017
2. TITLE SPONSORS TRACK SPONSORS
3. HEADLINE SPONSORS PARTNER SPONSORS MEMBER SPONSORS Baker Hostetler Bradford, LTD Capital One Coastal Cloud Colorado Impact Fund Connect For Health Colorado Cooley Corus360 EKS & H Event Integrity Full Contact Gary Community Investments General Assembly Groundfloor Media / CenterTable Guiceworks ImageSeller Ink Monstr Intelivideo Luna Gourmet Coffee & Tea Nanno Office of Economic Development Pass Gas Denver Slalom Wazee Digital Accenture Bridgepoint Education Butler Snow Delta Tables Hogan Lovells Meyer Law Name.com Slifer Smith & Frampton SoGnar Sounddown Swiftpage The Denver Foundation Zipcar
4. TRAVIS NELSON -Partner / Software Architect at Moonsault Software -15 years in enterprise and startup experience -Denver Java Users Group - VP -Denver Microservices - Founder
5. WHAT ARE MICROSERVICES? MONOLITH https://martinfowler.com/articles/microservices.html MICROSERVICES
6. MONOLITH VS MICROSERVICE: SCALING MONOLITH MICROSERVICES https://martinfowler.com/articles/microservices.html
7. GOOGLE TRENDS: MICROSERVICES Past 5 years Martin Fowler Denver Microservices Neal Ford Neal Ford
8. HOW DO I USE MICROSERVICES FROM THE START?
9. MICROSERVICES FROM THE START
11. FIRST, STARTUPS NEED TO: -Figure out what people want. -Build what people want. -Sell what people want.
12. DON’T I NEED TO BE READY TO SCALE?
14. DOESN’T MICROSERVICES INCREASE PRODUCTIVITY? https://martinfowler.com/bliki/MicroservicePremium.html
15. MANAGEMENT SAID SO…
16. HOW DO I USE MICROSERVICES FROM THE START?
18. MONOLITH-FIRST STRATEGIES -Sacrificial Architecture
19. SACRIFICIAL ARCHITECTURE Just replace the monolith entirely
20. SACRIFICIAL ARCHITECTURE
21. SACRIFICIAL ARCHITECTURE
22. MONOLITH-FIRST STRATEGIES -Sacrificial Architecture -Peel off
23. PEEL OFF Starts with a monolith and gradually peels off microservices at the edges.
24. PEEL OFF
25. PEEL OFF Before After
26. MONOLITH-FIRST STRATEGIES -Sacrificial Architecture -Peel off -Coarse-grained Services
27. COARSE-GRAINED SERVICES - Get used to working with multiple services - Reduces the amount of inter-service refactoring you have to do
28. COARSE-GRAINED SERVICES
29. COARSE-GRAINED SERVICES
30. THE PATH TO MICROSERVICES?
31. MY ADVICE -Automate early -Deploy often -Keep it simple -Rewrite
32. PATH TO SUCCESS
33. DENVER MICROSERVICES MEETUP
34. QUESTIONS? -travis@moonsault.co -denvermicroservices.com