I think it is clear to everyone at this point that the orchestrator_news_service microservice is a hollow component, which serves us only to orchestrate the data. Thus, there is no great advantage in performing individual tests to find points of failure.
The test that we perform is about the actual behavior of a consumer of our microservices. We have created tests with microservices written in Flask earlier in this chapter.
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