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.
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.
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.
![Kodak Black - Versatile 4 [Official Video]](http://i.ytimg.com/vi/VcP_1Ua__vY/mqdefault.jpg)
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.
I completely agree. My startup is considering going with an ACA solution.
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.
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.
Probably great video, but had to bail cus of background music