I'm currently weighing different options on Azure for an upcoming migration and could use some insight on cost efficiency. We have CIS v8 control requirements that mandate inspection and monitoring of incoming traffic. Right now, we are primarily a Windows Server environment, which makes automating maintenance tasks a bit tricky.
One specific use case I'm looking at is Keeper Automator, a lightweight service that needs to run 24/7 to manage requests from our password manager. It's currently running on Azure Container Apps (ACA) with minimal specs, but even with that setup, costs are adding up due to the need for internal load balancers and constant operation.
I might have more use cases for ACA later, but I want to avoid any unwelcome surprises in expenses during our migration. Would switching to an App Service be more economical? I don't know much about App Service yet and initially thought ACA was the cheaper route. Or should I just go for a B2s VM and set up port forwarding? I'm open to any guidance on which option would be the best for my scenario!
3 Answers
It sounds like you might actually benefit from an Azure Function App instead. If your workload isn’t super constant and you can trigger actions on-demand, the Consumption plan could be really cost-effective. But if you need something running 24/7, then a B1 tier App Service is a solid choice – it's around $13 a month and can handle your needs without issues. It seems like ACA might be overcomplicating things for your use case, especially if you're not utilizing its full range of features. I would steer clear of VMs; they can definitely add up and generally aren't the best option for lightweight tasks like yours.
Absolutely, App Service could be ideal here. We deploy similar lightweight apps and websites using App Service all the time, and it scales nicely with demand. However, I understand you have some concerns about your current network setup.
If you’re using private networking with a hub-and-spoke model, you might still be able to set up private endpoints with App Service, but it could get pricy if you have to resort to running an App Service Environment, which can rack up costs pretty quickly. Stay mindful of how those expenses stack up against a straight VM solution, which might offer a more straightforward setup for your needs.
I looked into App Service in relation to our private networking, and yeah, it made me hesitate a bit too because I felt like I'd hit a wall with the networking configurations. Let’s see if I can leverage ACA’s internal load balancing better, but man, it can be a balancing act with costs.
Honestly, both ACA and App Service can work for Keeper Automator, and each has its own strengths. ACA gives you that more hands-on control over containers which can feel 'simpler' in some cases. But if you're keeping track of costs, remember that you'll have the extra expense of the Internal Load Balancer with ACA. Compare this with the App Service Linux costs, factoring in your RAM and cores, to make sure you’re not overlooking something!
Keeper Automator really does need to run continuously, so I get why you’re cautious about Function Apps. The real-time processing it requires won’t sit well with spin-up times, right? It does sound like App Service might offer the right balance for constant availability without the extra overhead of running a VM.