With the desire to not create friction for consumers of microservices, developers often come up with strategies to infer data. Do not be afraid to create friction. A microservice, at its endpoint, must receive all the necessary information for the complete execution of the task for which it was created.
Trying to work with microservices using inconsistent or poor data is the same as getting into a taxi and telling the driver to guess where he should take you.
Get Microservice Patterns and Best Practices now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
Get Mark Richards’s Software Architecture Patterns ebook to better understand how to design components—and how they should interact.
Dive in for free with a 10-day trial of the O’Reilly learning platform—then explore all the other resources our members count on to build skills and solve problems every day.
Start your free trial Become a member now