Please log in to watch this conference skillscast.
An essential principle of the microservice architecture is loose coupling. Ignoring this principle is a surefire way to becoming yet another "microservices failure story”. In this talk you will learn about the different kinds of coupling, how to minimize design time and increase the productivity of your teams.
The microservice architecture is a key part of cloud native. An essential principle of the microservice architecture is loose coupling. If you ignore this principle and develop tightly coupled services the result will mostly likely be yet another "microservices failure story”. Your application will be brittle and have all of the disadvantages of both the monolithic and microservice architectures.
In this talk you will learn about the different kinds of coupling and how to design loosely coupled microservices. I describe how to minimize design time and increase the productivity of your DevOps teams. You will learn how to reduce runtime coupling and improve availability. I describe how to improve availability by minimizing the coupling caused by your infrastructure.
YOU MAY ALSO LIKE:
- Keynote: Not Just Events: Developing Asynchronous Microservices (SkillsCast recorded in November 2018)
- Better Software Faster with Dave Farley (Online Course on 8th - 9th February 2021)
- Microservices Architecture with Jorge Ortiz‑Fuentes (Online Course on 15th - 17th February 2021)
- μCon: The Microservices eXchange (Online Conference on 13th - 14th April 2021)
- Introducing AWS Immersion Days (Online Meetup on 11th February 2021)
- Evolutionary Architecture (SkillsCast recorded in January 2021)
- What an Architect Can Learn from Retrospective Failures (SkillsCast recorded in December 2020)
Designing Loosely Coupled Microservices
Chris Richardson is a developer and architect. He is a Java Champion, a JavaOne rock star and the author of POJOs in Action, which describes how to build enterprise Java applications with frameworks such as Spring and Hibernate.