Why Azure Container Apps might give a better end-user experience than Azure Function Apps.

In this video I show you a blog post I like. It discusses why Azure Container Apps (ACA) might give a better end-user experience than Azure Function Apps but also why ACA might be cheaper.

Resource:

[BillSpaulding-xi]

thank you for the video. as a workaround. the cold start behavior starts after 5 minute idle. you can deploy a timer trigger and fire it every 4 minutes. the service invocations are covered in the number of free calls provided monthly in the consumption plan.

[Laughbankrip]

I completely agree. My startup is considering going with an ACA solution.

[BrendanAlexander]

Very helpful thank u! I have a small cluster of VMs to run an app consisting of a number of microservices. I dont use Kubernetes but rather docker swarm for orchestration, which is easy enough. Looks like Azure Container Apps would even easier to manage, and possibly cheaper.

[ehvlullo]

Some good considerations mentioned in this video. However I dare say people need to start looking at their architecture a bit more critically. Why do we feel the need to have this micro-services-jungle with such cascading service calls that all take time and have some risk following a single user click? And then we get added complexity where now people are suggesting adding CRON jobs just to keep UX acceptable. Where possibly this whole thing could have been 1 DB with 1 Azure App service to begin with. Complexity can kill.

[rooroont]

Probably great video, but had to bail cus of background music