Here are some of my notes and related thoughts.

How to break a Monolith into Microservices. To quote Martin Fowler: Many development teams have found the microservices architectural style to be a superior approach to a monolithic architecture. Much has been written on the pros and cons of microservices, but unfortunately I’m still seeing them as something being pursued in a cargo cult fashion in the growth-stage I just watched Martin Fowler's talk about Microservices at XConf.

If so, you’ve likely started to encounter the trade-offs. Intro. This is the story of that transition from monolith to microservices at one of the world’s biggest e-commerce platforms—what we learned, what worked, and how you can learn from our experience—while highlighting two keys in our transformation success: focusing on culture, and using Martin Fowler's Strangler Pattern. Martin Fowler. The urge to chisel away the monolith is guided by philosophies such as Conway's Law, which states that a system mimics its communication structure, and by thought leaders such as Martin Fowler, who has spearheaded thought on microservices architecture. The good news is that since Martin’s article, the technology to operate a microservices architecture has evolved rapidly. – Simon Brown. Such an approach can leave a substantial monolith at the heart of the microservices architecture, but with most new development occurring in the microservices while the monolith is relatively quiescent. If you’ve built a monolith or two of your own, you’ve probably started looking for ways to blow it up using microservices. 3 June 2015.

– Martin Fowler. MonolithFirst.

If you can’t build a well-structured monolith, what makes you think microservices is the answer? evolutionary design. ... For more on this operational readiness see Martin Fowler’s article on Microservices prerequisites.