We spend ~900$ a month on fargate to run our of our dev, stage, qa, and prod environments as well as some other services and sqs consumers. After the recent price decrease we looked at how much reserve instance would save us and the few hundred in savings would not make sense vs the over provisioning and need to dedicate resources to scaling and new tools to monitor individual containers.
Note: do have some stuff in lambda but its package size restrictions limit us.
We're talking about Lambda tho, executing a function, how much code is required to execute a function... The largest .net lambda I've managed to create is ~40mb which included chromium.
While Lambda is sold as “functions as a service” I have on several occasions made the particular function being served the router for a Ruby web application - with the Ruby runtime there’s really nothing stopping you running a complete Rails app in Lambda other than size limitations once you add a few too many gems.
Well it depends what that function is doing. Do I need a full word2vec mapping? I've got small bits of data that would blow past that limit compressed despite the work I want done being a single easy function call.
Note: do have some stuff in lambda but its package size restrictions limit us.