Thank you Atul. Appreciate the thoughtful feedback. Completely agree that most of the work in these migrations ends up being around the platform and deployment model rather than the application itself. Interesting to hear about your EC2 → ECS Fargate experience as well. Glad you found the post useful, and all the best with your technical writing journey! I will check those for sure

Thanks, Atul. Glad you found it useful. From an operational perspective, I'd say observability became simpler overall. We now rely primarily on Azure Log Analytics and Container Apps diagnostics instead of SSH-ing into a VM and inspecting logs directly. There was a bit of a learning curve initially, but once everything was wired up, troubleshooting became more centralized. As for gotchas, the biggest ones for us were actually during deployment rather than runtime: • Azure Student subscription restrictions around ACR cloud builds ("az acr build") • ARM64 vs AMD64 image compatibility when building on Apple Silicon • Rethinking configuration management when moving away from server-hosted ".env" files Regarding cold starts, we chose not to scale to zero. We configured a minimum replica count of 1 because API responsiveness was more important for us than squeezing out every last bit of cost savings. Given our current traffic profile, that felt like the right tradeoff. So far, ACA has been a good fit because it removes most of the infrastructure management overhead while still letting us keep a container-centric deployment model. I'm sure we'll discover more tradeoffs as the platform grows, but the migration has been positive overall.