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

Is the server/host-side available as library for self hosting? #60

Open
Danielku15 opened this issue May 8, 2021 · 2 comments
Open
Labels

Comments

@Danielku15
Copy link

Description

I understand that the azure relay is primarily a service for exposing locally operated services via Azure. The system seems well maintained and is having a well documented protocol in place. We have basically the same requirement for our services which are not only hosted in Azure but also operated fully on-premises on an own infrastructure.

Currently we have an own library which is doing basically the same as azure relay but you can self host the server side. You can have an ASP.net core application on the edge accepting requests from both end users and also the exposed applications. Then via a custom websocket based protocol we process the HTTP request on the private network service (also ASP.net core) and stream back/forth the request responses.

To avoid having this "home brew" solution I would like to fully build our solution on top of Azure Relay. While I have found the formal specification of the "Hybrid Connection" protocol, I haven't found a library (preferably ASP.net core) which would allow me to operate the edge side on my own.

Actual Behavior

There is no available library for hosting the edge server for Azure Relay services on my own.

Expected Behavior

I want to self host the Azure Relay edge side on my own via an ASP.net core middleware which is then ultimately operated via Kestrel or IIS. Configuration of the available namespaces and required keys would go via a custom services that to hook up the middleware with custom rules.

Even just a base framework would be a good starting point to build my own middleware but avoid the re-implementation of the whole protocol parts.

@Danielku15
Copy link
Author

Any feedback on this request?
@dlstucki @microsoftopensource

@manojprasad-ms
Copy link

No there aren't any plans to support this in the near term

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

No branches or pull requests

3 participants