5 ms·
I find it exhilarating, but you have to have a well architected distributed system. Some key points: - Your micro service should be able to run independently.
by jedberg 5y ago
I find it exhilarating, but you have to have a well architected distributed system. Some key points:
- Your micro service should be able to run independently. No shared data storage, no direct access into other microservices' storage.
- Your service should protect itself from other services, rejecting requests before it becomes overloaded.
- Your service should be lenient on the data it accepts from other services, but strict about what it sends.
- Your service should be a good citizen, employing good backoffs when other services it is calling appear overloaded.
- The API should be the contract and fully describe your service's relationship to the other services. You should absolutely collaborate with the engineers who make other services, but at the end of the day anything you agree on should be built into the API.
Generally if you follow these best practices, you shouldn't have to maintain a huge working knowledge of the system, only detailed knowledge of your part, which should be small enough to fit into your mental model.
There will be a small team of people responsible for the entire system and how it fits together, but ideally if everyone is following these practices, they won't need to know details of any system, only how to read the APIs and the call graph and how the pieces fit together.