July 2017
Beginner to intermediate
340 pages
7h 43m
English
We have said in Chapter 4, Designing Runnerly, that a safe approach to designing microservices is to avoid creating new ones without a good reason.
The database that holds user data is served by the DataService microservice, which is used by the Celery workers. The first option that comes to mind is to have a single Flask application, which manages that database, and serves both our end users with its HTML and JS content and other microservices with its JSON APIs.
The benefit of this approach is that we do not need to worry about implementing yet another network interaction between the dashboard and DataService. Moreover, besides the ReactJS app, there's not a lot we need to add on top of DataService to make ...