Go faster than your competitors. That’s the promise of microservices – deploy faster, scale faster, be more robust. It’s all about outcomes and the way your organisation is structured has a tremendous impact on those outcomes. it’s easy to say “Conway’s Law” and then move swiftly on. “But but but, but how?”

In early 2014, James and Martin Fowler called out “Organised around business capabilities“ as a core characteristic of microservices. This was based on feedback from successful teams around the world about how important this aspect was on the systems they were building. In this talk, James explores some of these structures and provides some practical guidance on what he and Martin meant when they said “business capability”.

About the Speaker(s)

I am currently a Principal Consultant for ThoughtWorks based in the UK where I have been working as a developer and coach introducing evolutionary architecture practices and agile software development techniques to various blue chip companies: Investment Banks, Publishers and media organisations. I studied Astrophysics in the 90’s but got sick of programming in Fortran – plus as a theoretical physicist I am a much better software engineer. Seventeen years of DBA, software engineering, design and architecture later I’ve turned into a bit if a greybeard. Not due to the requisite 20 years experience but through owning one. I am a member of the ThoughtWorks Technical Advisory Board providing advice to technology and business leaders within and without Thoughtworks in the areas of web integration, evolutionary architecture, emergent design and lean thinking. I’ve spoken at a number of national and international conferences on topics ranging from domain driven design, microservices, SOA and the future of the web to agile adoption patterns and lean thinking.