You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now created functions' endpoints must be made available to the end user/application, which could impose a security risk.
With an API Management service you could deploy API gateways side-by-side functions, optimizing the traffic flow and enforce compliance requirements upon all available functions. Not only this but you would get a clear overview of all internal and external APIs. (or functions) currently available.
"APIs are the foundation of an API Management service instance. Each API represents a set of operations available to app developers. Each API contains a reference to the backend service that implements the API, and its operations map to backend operations.
Operations in API Management are highly configurable, with control over URL mapping, query and path parameters, request and response content, and operation response caching." - Microsoft
馃帳 Pitch
I have extensive experience with API Management Service through my previous employment role as an Azure Integration Engineer.
Microsoft API Management service is very popular but relatively expensive when not ran on a consumption payment schedule. Implementing this into Appwrite will allow developers to publish API endpoints with some form of logic and compliance requirements, thereby improving the security and improving flexibility.
I believe that implementing a service such as this could be a real differentiator for Appwrite, as it will allow developers the flexibility that Azure offers but without being locked into their eco-system.
馃憖 Have you spent some time to check if this issue has been raised before?
馃敄 Feature description
Right now created functions' endpoints must be made available to the end user/application, which could impose a security risk.
With an API Management service you could deploy API gateways side-by-side functions, optimizing the traffic flow and enforce compliance requirements upon all available functions. Not only this but you would get a clear overview of all internal and external APIs. (or functions) currently available.
What I'm essentially proposing is something similar as Microsoft Azure API Management Service.
"APIs are the foundation of an API Management service instance. Each API represents a set of operations available to app developers. Each API contains a reference to the backend service that implements the API, and its operations map to backend operations.
Operations in API Management are highly configurable, with control over URL mapping, query and path parameters, request and response content, and operation response caching." - Microsoft
馃帳 Pitch
I have extensive experience with API Management Service through my previous employment role as an Azure Integration Engineer.
Microsoft API Management service is very popular but relatively expensive when not ran on a consumption payment schedule. Implementing this into Appwrite will allow developers to publish API endpoints with some form of logic and compliance requirements, thereby improving the security and improving flexibility.
I believe that implementing a service such as this could be a real differentiator for Appwrite, as it will allow developers the flexibility that Azure offers but without being locked into their eco-system.
馃憖 Have you spent some time to check if this issue has been raised before?
馃彚 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: