Skip to content
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

Qewd-up without websockets? #40

Open
grantforrester-nes opened this issue Jan 16, 2020 · 2 comments
Open

Qewd-up without websockets? #40

grantforrester-nes opened this issue Jan 16, 2020 · 2 comments

Comments

@grantforrester-nes
Copy link

Is it possible to configure the Orchestrator to forward incoming REST requests to a microservice using REST calls rather than websocket messages?

We are trying to integrate a non-Qewd service into an existing Qewd-up deployment.

Many thanks.
G

@robtweed
Copy link
Owner

To integrate an existing REST-based MicroService into a QEWD-Up architecture, you'd do it indirectly by either:

  • defining an API that is handled directly by the Orchestrator, and whose handler makes a REST request to the foreign MicroService (use the request module which QEWD has already loaded as a dependency)

  • define an API that is handled by a QEWD-Up MicroService, and the handler on that QEWD-Up microservice sends a REST request to the foreign MicroService.

Which option you use is up to you, but adding a QEWD-Up MicroService to provide the interface to the foreign MicroService would provide more flexibility if you want to intercept the flow by using Event Hooks

@grantforrester-nes
Copy link
Author

Option 1 looks like what I'm looking for.

Thanks for your help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants