Software developers and architects increasingly turn to microservices as a framework for improving the agility and velocity of their development efforts. But is it the right approach? This video presents a balanced view of the benefits and drawbacks of microservices. It outlines the motivations driving the adoption of microservices; compares and contrasts it to monolithic architecture; describes solutions to key problems such as inter-service communication and distributed data management; and moves on to a set of strategies for refactoring a monolithic application into a set of microservices.
Chris Richardson is a developer, architect, Java Champion, and JavaOne rock star. He wrote POJOs in Action (which describes how to build enterprise Java applications with frameworks such as Spring and Hibernate) and was the founder of the original CloudFoundry.com, an early Java PaaS for Amazon EC2. He is the creator of microservices.io and is working on his third startup: a platform for developing reactive microservices.
Clearing a path from developer to architect and enriching that path once you arrive.
Software architecture is a fast-moving, multidisciplinary subject where entire suites of "best practices" become obsolete practically overnight. No single path or curriculum exists, and different types of architecture—application, integration, enterprise—require different subject emphasis. Whether you’re at the outset of a career as an architect or in the midst of such a career, series editor Neal Ford has curated this collection of tools and guides for aspiring and seasoned architects alike.