-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate best approach for communication (queues, notification - pub sub model) between the API and microservices based on AWS technologies #1
Comments
Microservices that poll on the queue to receive the jobs
|
Message processing microservice fronts API Microservices. The message processor polls the queues and calls the APIs.
|
Alternatively, get rid of all the queues.
|
This is a very good read on Microservices architecture style But to flash this out a bit more we should also look into other Architecture styles Also worth reading this awesome API design guide about RESTful APIs. In particular the section about dealing with Asynchronous operations.
10 Design Principles for AWS Cloud Architecture
Queue-Based Load Leveling pattern
TL;DR: we don’t have to use microservices - we could use |
Will write up an ADR around this with an updated diagram in infrastructure. |
* bbc/digital-paper-edit-api#1 adding diagrams and updated ADR * Updated diagram * updated adr for option 3 * Update docs/adr/2019-04-23-transcript-architecture.md Co-Authored-By: Pietro <[email protected]> * Update docs/adr/2019-04-23-transcript-architecture.md Co-Authored-By: Pietro <[email protected]> * Updated with more details * Adding heading to each diagram * Spelling error fix and added another change in option 3 * Review done by Pietro - adding final conclusion
Context
Deciding the best approach for communication between microservices and API.
Acceptance Criteria
Decide and create an ADR around this.
Things to consider
The text was updated successfully, but these errors were encountered: