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.

Sign up for GitHub

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

Jump to bottom

First steps with one interaction - ie: confirm purchase #1

Open

5 of 7 tasks

treeder opened this issue Jun 26, 2019 · 0 comments

Open

5 of 7 tasks

First steps with one interaction - ie: confirm purchase #1

treeder opened this issue Jun 26, 2019 · 0 comments

Owner

treeder commented Jun 26, 2019 •

edited

AsyncAPI spec:

publish: order event (from user via UI)
subscribe: fulfillment subscribes to order event (doesn't have to do anything yet other than get it)
generate publish and subscribe clients

UI with one page with a button:

User clicks confirm purchase which sends event to server, uses generated publish code

Server (or direct to message broker?):

Push event into channel "orders". (what about authentication? what format if direct to broker? How does generated code know what format to use? this is why some http proxy might be really nice)
- Could start with nats: https://hub.docker.com/_/nats/

Fulfilment server:

subscribes to "orders" using generated code
just prints something to console for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment