November 19, 2016 at 10:08PM
"[M]icroservices architecture design takes a 'messages first' approach." #readingToday

When it comes to specification, microservices architecture design takes a 'messages first' approach. Ironically, you do not start by asking what services to build; you start by asking what messages the services will exchange. Once you have the messages, natural groupings suggest what services you need to build. This gives you a direct route from business requirements to implementation. (In my book, I argue that a design approach that accommodates under-specification is the winning strategy.)

Richard re-acquaints us with science and engineering embodied as components and looks at the key concepts of microservices.