Building Microservices the right way

Transcript

1. Building Microservices the right way Chibuike Nwachukwu
2. About me Software Engineer at Payrix, Technical Writer and AWS Community Builder (2x AWS Certified) - Chibuike Nwachukwu
3. Building Microservices the right way Chibuike Nwachukwu
4. What are Microservices? It is an architectural pattern that structures an application as a collection of services Microservices are self contained and independent
6. Benefits of Microservices Loosely Coupled Flexible scaling Easy Deployment Technological Freedom Resilience Agility
7. Outline • Microservices and its Benefits • Building Microservices the right way • Wrap up • Additional Resource
8. Building Microservices the right way • Domain-Driven Design • Resource Separation • Asynchronous Communication • Detailed Documentation
9. The golden rule: can you make a change to a service and deploy it by itself without changing anything else? ― Sam Newman, Building Microservices: Designing Fine-Grained Systems
10. Domain-Driven Design Building Microservices the right way
11. Domain-Driven Design Here each microservice is designed around the business needs, each focuses on a particular business need and builds around it. Here the concept of Single responsibility comes to play where each microservice is tasked with carrying out a “single” responsibility in the system. Serverless/Functional architecture shares concept with this since it also encourages a function/service doing a singular thing.
12. Benefits of Domain-Driven Design • Standard Communication: Communication between developers and teams becomes much easier. Ubiquitous language is likely to contain simpler terms developers refer to, no need for complicated technical terms. • More flexibility: Thanks to this, the entire system can be modified and improved regularly. • Better product: Engineers understand business domains well.
13. Case Study: Fiverr
14. Resource Separation Building Microservices the right way
15. Resource Separation A Microservice should be completely contained, containing all the resources it needs to work. Separating both human and technological resources like storage, database, repository, deployment tools having them dedicated to each microservice
16. Benefits of Resource Separation To Engineers • Increases agility • Improves productivity • Increases skill-set • Increases product knowledge • More accountability To application • Increases resilience • Improves security • Better management and governance • Removes interdependency • Improves performance
17. Resource Separation
18. Asynchronous Communication Building Microservices the right way
19. Asynchronous Communication This is a non-blocking protocol that follows event-driven architecture. It allows parallel execution of requests and provides better resilience. Synchronous interactions: Dominates the closer you get to a user (like with a website) Asynchronous Interactions: Should become the rule if there is any work that can be deferred, when interaction is between the services
20. Benefits of Asynchronous Communication To users • Saves time • Improves User Experience • Increase in site usage To application • Faster applications • Better performance • Saves Cost
22. Detailed Documentation Building Microservices the right way
23. “I'm writing this so that someone can understand what I did”
24. Detailed Documentation Everything should be written down imagining the author won’t be available ever again. Increased demand for performance and dynamic approach requires advanced monitoring This also helps track the flow of events within the architecture easily using RFC, Open APi Spec, Documentation, Readme
25. What should be documented? Everything should be documented, Architectural documentation, Technical Requirement documentation, APi Spec etc
26. Benefits of Detailed Documentation • Acts as a source of Truth • Cultivates a Good Work Culture • Frees up Human Resource. • Helps Onboard Engineers faster • Makes Team Agile as they own their own systems
27. Wrap Up
28. Wrap Up • We learnt about Microservices and its Benefits • We discussed best practices to use when building such
29. Additional Resource • EBook - Microservices Patterns by Chris Richardson • Website - NetFlix Engineering Blog • Community- Aws UG, AWS Community Builders, etc • E-learning courses - InterviewReady
30. Thank You /chibuikenwachukwu /chyke007 @botChyke