-
Notifications
You must be signed in to change notification settings - Fork 4
Description
Description
Currently, Gateway consists of the following separate apps:
- account-api
- account-worker
- content-publishing-api
- content-publishing-worker
- content-watcher
- graph-api
- graph-worker
Each "-api" app is focused on serving RESTful service endpoints and submitting jobs to worker queues; each "-worker" focuses on processing a dedicated set of queues.
*Note: content-watcher is a hybrid app that has both endpoints and queues
This structure means that, downstream we have multiple Docker images corresponding to the different apps. It also means that, even in cases of very little load for testing, QA, light use deployments, etc, it is necessary to stand up multiple pieces of infrastructure depending on which services you require.
A better approach might be to transform Gateway into a single app, with the available endpoints and active queues to process controlled via the app configuration. This would allow for a single Docker image to be published, and greatly reduced infrastructure overhead for non-production (and even small production) deployments.