Part 1 of 8 · 1 min read
Why this page comes seventh
In this module you will
- State four rules for a good service interface and the reason behind each.
- Explain why a shared database is a poor way to connect services.
- Choose between synchronous and asynchronous, request and response or events, orchestration or choreography.
- Compare RPC and REST, and say what each does to coupling.
- Change an interface without breaking its callers: tolerant readers, semantic versions, coexisting endpoints.
Page 5 said that services must talk to each other only over the network, and page 6 drew the boundaries. This page covers how the talking works. The interface is the part of a service that other teams depend on, so a poor choice here is paid for by many people for a long time. The book used is "Building Microservices" (BM), chapter 4, with a link back to the page 4 styles from "Fundamentals of Software Architecture" (FSA). The numbers are made up to show the idea, unless the text names a book.