We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Interaction with modules will be managed by HTTP facade part of the fabric with the following responsibilities:
The text was updated successfully, but these errors were encountered:
Postpone since the inter-cluster module calls will be done using Ignite Thin Client
Sorry, something went wrong.
Consider using Azure Functions HTTP triggers as the Facade rather than extending Fabric
Azure Functions were dropped as well, but it is possible to integrate Perper directly with an ASP.NET Host, thus serving as an HTTP facade.
I don't believe we need to do anything for this, except perhaps provide a sample/documentation. Retagging accordingly.
No branches or pull requests
Interaction with modules will be managed by HTTP facade part of the fabric with the following responsibilities:
The text was updated successfully, but these errors were encountered: