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

Can Krakend handle Api Orchestration support concurrent mode and sequential mode in one endpoint (mix mode) #595

Closed
chchgb opened this issue Jul 28, 2022 · 3 comments

Comments

@chchgb
Copy link

chchgb commented Jul 28, 2022

Is there anyone can help me to build one endpoint with below scenario?

backend A -----> backend B(rely on the result from A) -----> backend D(rely on the result from both B and C)
-----> backend C(rely on the result from A)

much like the mix model in rule engine

similar issues:
krakend/krakend-ce#176
#182

@alombarte
Copy link
Member

Hi @chchgb , you can achieve this by creating intermediate endpoints, but there are no plans to support this feature using a single endpoint

@github-actions
Copy link

Hi, thank you for bringing this issue to our attention.

Many factors influence our product roadmaps and determine the features, fixes, and suggestions we implement.
When deciding what to prioritize and work on, we combine your feedback and suggestions with insights from our development team, product analytics, research findings, and more.

This information, combined with our product vision, determines what we implement and its priority order. Unfortunately, we don't foresee this issue progressing any further in the short-medium term, and we are closing it.

While this issue is now closed, we continue monitoring requests for our future roadmap, including this one.

If you have additional information you would like to provide, please share.


This is an automated comment. Responding to the bot or mentioning it won't have any effect

@github-actions
Copy link

This issue was marked as resolved a long time ago and now has been automatically locked as there has not been any recent activity after it. You can still open a new issue and reference this link.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants