richardrodger-designing-microservices-london-may.pdf
0 likes6 views
The document discusses the design and architecture of microservices, specifically focusing on how to determine which microservices to build based on requirements, messages, and services. It illustrates the interaction between services using visual conventions and provides examples, such as a search engine for Node.js modules. The author, Richard Rodger, emphasizes the distinction between synchronous and asynchronous communication in microservices.
richardrodger-designing-microservices-london-may.pdf
- 1. Designing Microservices A visual language for service description Richard Rodger @rjrodger
- 2. How do you decide which microservices to build?
- 4. "Build a user registration page"
- 5. Requirements àč a) capture user details àč b) send confirmation email
- 6. Requirements àč a) capture user details àč b) send confirmation email Messages àč a) register-user: {name: ..., email: ...} àč b) confirm-email: {email: ...}
- 7. Requirements àč a) capture user details àč b) send confirmation email Messages àč a) register-user: {name: ..., email: ...} àč b) confirm-email: {email: ...} Services àč registration sends register-user to user àč user sends confirm-email to mailer
- 8. user registration mailer register-user confirm-email
- 9. When do you need an answer? àčNow: synchronous àčNever: asynchronous
- 10. Who does the work? àčOne: message consumed àčMany: message observed
- 11. micro- service A micro- service B solid line means synchronous solid arrow means consumed hexagons are microservices synchronous/consumed request-response
- 12. micro- service A micro- service B dashed line means asynchronous empty arrow means observed asynchronous/observed publish-subscribe
- 13. micro- service A micro- service B solid line means synchronous empty arrow means observed synchronous/observed sidewinder
- 14. micro- service A micro- service B dashed line means asynchronous solid arrow means consumed asynchronous/consumed winner-take-all
- 15. Visual conventions Service Synchronous Message Asynchronous Message Consumed Message Observed Message
- 17. Let's build a Search Engine for Node.js modules... Business Requirements: àč a) search for Node.js modules àč b) index published Node.js modules àč c) show Node.js module details
- 20. Requirements àč a) search for Node.js modules Messages àč role:search,cmd:search (sync+consume) Services àč web sends role:search,cmd:search to search
- 22. Requirements àč b) index published Node.js modules Messages àč role:search,cmd:insert (async+observe) Services àč npm sends role:search,cmd:insert to search
- 24. Requirements àč c) show Node.js module details Messages àč role:info,cmd:get (sync+consume) Services àč web sends role:info,cmd:get to info
- 26. Requirements àč c) show Node.js module details Messages àč role:info,need:part (async+observe) àč role:info,collect:part (async+observe) Services àč info sends role:info,need:part to npm, github àč npm, github send role:info,collect:part to info
- 29. Demo!
- 30. A search engine for Node.js modules: github.com/nodezoo senecajs.org