Examining the next functionality of filtering books seems to be coming under the purview of the book catalog microservice itself. However, having said that, let's confirm it by questioning our own understanding of the business domain here. The question that comes to my mind is related to the impact of all the searches that our users would perform, bringing down the service. So should the book search functionality be a different service? Here the answer lies in the fact that the microservice should have its own data store. Having the book catalog and the book catalog search function as different services would require us to maintain a list of books in two different locations with additional challenges, such ...
The book-searching microservice
Get Building Microservices with .NET Core 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.
