This articles best points, for me, cover some guidelines for how to approach building software systems where gaining the advantages of microservices are something you might want to achieve. As such the points that chimed most with me were:
"If you want convenience, build a monolith. They are significantly quicker to start a new project with, quicker to be able to alter the service boundaries as desired. To be able to get that initial jolt of primary development, they are the right answer.
For more sustained innovation and ability to change anything as desired, you must work to reduce the sharing between areas of the system to allow them to move independently of each other. Our life preserver design process and tool takes relative rates of change as the core concept, and so was built to guide this process. It’s ideal for figuring out how to build microservices."