Loose coupling
Loose coupling is a software design approach that implies every part of an application should know little information about the other parts. In traditional applications, if you write a GUI component, such as a button, it has to be possible to use it everywhere, for any application. As another example, if you develop a library to work with sound hardware, this also means you can use it with every application; the library is not limited to use in one kind of application. In microservices, however, loose coupling means that a microservice doesn't know anything about other microservices, or how many there are.
If you develop an application, you should write parts of it—microservices—as standalone applications. For example, a notification ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access