Matthew Skelton has been building, deploying, and operating commercial software systems since 1998. Co-founder and Principal Consultant at Skelton Thatcher Consulting (http://skeltonthatcher.com/), he specialises in helping organisations to adopt and sustain good practices for building and operating software systems: Continuous Delivery, DevOps, aspects of ITIL, and software operability.
Matthew curates the well-known DevOps team topologies patterns at devopstopologies.com and is co-author of the books Database Lifecycle Management (Redgate, 2015), Continuous Delivery with Windows and .NET (O’Reilly, 2016), and Team Guide to Software Operability (Skelton Thatcher Publications, 2016).
How to break apart a monolithic system safely without destroying your team
Moving from a monolith to microservices can be daunting. How do we choose the right bounded contexts? How small should services be? Which teams should get which services? And how do we keep things from falling apart?
By starting with the needs of the team, we can infer some useful heuristics for evolving from a monolithic architecture to a set of more loosely coupled services.