5 ms·

Well we went with AWS for this current project because they offered good/free ‘first year pricing, and now we are being bitten by them a little, our workload is

Well we went with AWS for this current project because they offered good/free ‘first year pricing, and now we are being bitten by them a little, our workload is not huge but when you’re bootstrapped these kinds of costs add up, and they’re especially pernicious because it hasn’t made sense financially for us to pay someone to optimize them lower. Hence my concern to make good decisions early on this new project. We use Stripe and it has also served us well so far. The development team is mostly FE focussed and we have limited access to a dedicated DevOps engineer which is why I’m keen to keep that aspect of the stack as ‘standard’ as possible

p_l 5y ago
Well, I'd look into ways to get off the AWS train then. You're already in better starting position given the use of ECS, so you have some preparation for running containers. Since AWS is too expensive, I figure Heroku is right out, and it pushes towards cost optimization a lot. Personally I'd go with some low-cost hosted kubernetes so long as the provider also includes database hosting and integrates logging and such - this means avoiding some of the most complex for starters tasks of handling it - but I also already have k8s experience. Despite what some people say it doesn't have to be complex, but I'd consult with whoever you have available regarding operations - who knows, they might offer some services you didn't know about before. Keeping to something like "twelve factor app" will help to keep your stack simple to deploy no matter which way you go, IMO.