You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a Mojaloop Community member I want to have a performant quoting service so that I can scale the quoting servce
Note: The current quote service performs this action in memory, and a better solution would be to split the servce into two microservices with Kafka events. This will decouple the participant API responses from the work being perfromed and free's up the nodeJS event loop.
Verify the Quote service is split into two microservices namely an quotes API service and and quotes handler service
Verify that a configurable kafka topic is used to pass messages between the servcies (kafka configuration should follow same pattern as central ledger)
Verify that the GP test pass
Verfy that there is a new runtime CLI option (using commander lib; same as central ledger)
Verfy that a health endpoint is added to the new servces
Complexity: <High|Medium|Low> > A short comment to remind the reason for the rating
Uncertainty: <High|Medium|Low> > A short comment to remind the reason for the rating
Tasks:
Define proper Kafka config for Producers and Consumer
Update logic of API handlers to publish a payload into separate kafka queues (quotes/bulk_quotes get/put/post)
Create a consumer to handle all new kafka topics
Add/update unit-tests
Update test-harness to use a new version of Quoting service
@PaulGregoryBaker and @geka-evk , thanks for this issue. Please bring this up at the DA at the earliest; I'm not opposed to this and it makes sense but it is a significant change.
Goal:
As a
Mojaloop Community memberI want to
have a performant quoting serviceso that
I can scale the quoting servceNote: The current quote service performs this action in memory, and a better solution would be to split the servce into two microservices with Kafka events. This will decouple the participant API responses from the work being perfromed and free's up the nodeJS event loop.
Private Zenhub Image
Acceptance Criteria:
Complexity: <High|Medium|Low> > A short comment to remind the reason for the rating
Uncertainty: <High|Medium|Low> > A short comment to remind the reason for the rating
Tasks:
Done
Pull Requests:
Follow-up:
Dependencies:
Accountability:
The text was updated successfully, but these errors were encountered: