Skip to content

Conversation

@daixiang0
Copy link
Contributor

@daixiang0 daixiang0 commented Aug 20, 2024

Signed-off-by: Loong <loong.dai@intel.com>
@daixiang0 daixiang0 changed the title proposal: AI gateway API rfc: AI gateway API Aug 20, 2024
@tedivm
Copy link

tedivm commented Aug 20, 2024

I really think we should look at the open source Kong AI Gateway for this, as it has a lot of fantastic functionality.

@daixiang0
Copy link
Contributor Author

I really think we should look at the open source Kong AI Gateway for this, as it has a lot of fantastic functionality.

As an open-source ecosystem orchestration framework, OPEA should not bind one gateway.

The goal of OPEA is to accelerate AI land rather than bringing new cost like learn/maintain new gateway, a lot of enterprise has their own gateway solution team, migration is a cost. It can help enterprise minimize investment and maximize use of existing resources.

Kong open source gateway is good, but some powerful features are not open source, if we bind Kong, we need to find way to implement them while a new gateway implement is not our goal.

So the AI Gateway API provides a abstraction layer to use popular gateway solution, like Kong, Envoy, APISIX or others.

At the same time, it would get more potential partners who has their own AI gateway solution.

@ftian1
Copy link
Collaborator

ftian1 commented Oct 11, 2024

I will merge this PR. if we have further discussion, we can refine this one.

@ftian1 ftian1 merged commit 41a096f into opea-project:main Oct 11, 2024
@daixiang0 daixiang0 deleted the gateway branch October 11, 2024 01:30
@daixiang0
Copy link
Contributor Author

@ftian1 thanks

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

Successfully merging this pull request may close these issues.

4 participants