Microservices envy at Lisbon DDD Meetup
•
0 likes•120 views
A talk about the pitfalls that a microservices architecture can lead you to. Sharing my experience and view on what Microservices are and what you need to cater for to accomplish a successful usage of it. Also very much relevant to the Domain Driven Design usage when taking care of a growing organization with monoliths and an increased demand from stakeholders. An additional remark that this talk was not intended to discuss what K8s is or what technology to choose. Was rather on my experience running multiple services in production and trying to avoid monoliths.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Microservices envy at Lisbon DDD Meetup
Similar to Microservices envy at Lisbon DDD Meetup (20)
Recently uploaded
Recently uploaded (20)
Microservices envy at Lisbon DDD Meetup
- 4. “Kubernetes is an open source project that enables software teams of all sizes, from a small startup to a Fortune 100 company, to automate deploying, scaling, and managing applications on a group or cluster of server machines. These applications can include everything from internal-facing web applications like a content management system to marquee web properties like Gmail to big data processing.” @andrejaleixo Joe Beda CTO at Heptio Craig McLuckie & Brendan Burns K8s original developers https://enterprisersproject.com/article/2017/10/how-explain-kubernetes-plain-english
- 5. about myself André Aleixo Engineering Director at OLX Group @andrejaleixo
- 6. how do you describe microservices?
- 8. size Often times related to the piece of software But, more important than that Is the size of the team who maintains it team of half-a-dozen would support half-a-dozen services. Martin Fowler “
- 9. Smaller Teams owning (several) components https://less.works
- 10. data Data should be one of the very first things to assess in a microservice architecture No more shared databases A microservice implements a Single Bounded Context Sam Newman “
- 11. Decentralized data management + Polyglot Persistence Martin Fowler
- 12. Identifying Bounded Contexts and not depending from shared Model Representations Martin Fowler
- 13. operation When developing and deploying a microservice we should not consider dependencies as a priority. Consider what kind of events it consumes and emits Scaling with state is harder Stateless would scale gracefully Built and deployed independently. Stateless, with state as backing services 12factor.net “
- 14. Scaling of Monoliths vs Microservices Martin Fowler
- 16. up down in out Scale in/out and up/down
- 17. size → organization data → domains operation → cont. delivery quick recap
- 21. autonomy = ?
- 22. autonomy = ↓ coordination
- 23. autonomy = ↓ coordination ↑ releases
- 24. autonomy = ↓ coordination ↑ releases ↑ speed
- 26. If they are independently deployable, new versions might be released without dependencies b v2 a v1 c v1 d v1 Version bumped What happens to service C? Will it break? @andrejaleixo
- 27. If one team owns one service, then it means they are autonomous - less need for coordination b v2 a v1 c v1 d v1 @andrejaleixo
- 29. Our big gray boxy Monolith @andrejaleixo
- 30. Break it into small beautiful Microservices @andrejaleixo
- 31. But not just one, several of them! @andrejaleixo
- 34. Rest API Search Index Rest API Moderation Panel Storage Rest API Invoice Storage AntiCorruption AntiCorruption AntiCorruption Rest API User Storage AntiCorruption Transport Layer Transport Layer @andrejaleixo Rest API Online Transaction Storage AntiCorruption External Payment Gateway
- 47. Quality Gates Quality Scorecard Allows for continuous improvement and pre-commit alerts on decreased quality Size vs Coverage ratio: smaller and greener is better
- 48. A good microservice designer understands the need for adaptability and endeavors to continually improve the system instead of working simply to produce a solution “ The Systems Approach to Microservices Book
- 50. Appendices
- 51. Workspace Build Report Publish CD pipeline SCM Build configuration tools Verify Registries CI server QA tool Test Package used to resolve dependencies
- 52. RoseKeeperBusiness Tool API Gateway Advert Message Bus Transponder Taxonomy BackEnd PostOffice MarketplaceAuth Mercury µservices Marketplace Business Tool Sync Requests Async Requests Happy Path for Publishing Process/Flow where an Advert coming from an API consumer Tool in a specific Marketplace Example: Publish an Advert
- 53. Tracing Example