Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted May 02, 2024 - 11:00 UTC
Scheduled
CONTEXT: Our UbiFunction/Plugins modules use API Gateways to integrate with the underlying serverless infrastructure provider. Today an UbiFunction/Plugin execution flows is:
HTTP Request => Kong (1st API Gateway) => Argo (2nd API Gateway) => Serverless infrastructure provider.
The 1st API Gateway often suffers of latencies and it has increasingly become a scalability bottleneck because of the amount of requests received in UbiFunctions/Plugins.
WHAT WILL BE DONE? We will deprecate "Kong (1st API Gateway)" and leave only "Argo (2nd API Gateway)" which has been already tested against the traffic seen in the module, and passed our scalability criteria.