I’d really love to know more about the 15% slower. Was it lambda@edge? Where were your api gateways? And is each invocation handling only one 3.5ms request or are you batching them? Since lambda bills to 100ms, it almost sounds necessary to batch here, but it may not fit your app
-
-
-
Not my blog post, just sharing :)
Kraj razgovora
Novi razgovor -
-
-
When you were running your performance comparisons did you ever set your Serverless solution to be the active deployment which your production traffic ran through? And how long were you running the tests for?
-
Not my blog post, just sharing :)
Kraj razgovora
Novi razgovor -
-
-
Serverless with AWS ... no every cloud ...
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Made a similar experience. On top of that it turned out that azure functions aren’t really serverless. We had to manage the underlying app service plan. We switched to self hosted in Kubernetes, deployed with helm charts.
-
Is there a particular reason you chose the App Service plan? Azure Functions are “truly Serverless” when using the Consumption and Premium plans.https://docs.microsoft.com/en-us/azure/azure-functions/functions-scale …
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
Server Guy
Ultrarunner