[btreecat]

Neat tool!

Not sure I agree with the choices on the AWS side, particularly lambda and dynamo. They seem great when you first start, but I've found the pain comes with maturing code.

As professionals, we should always plan for our code to live longer than we thought originally, and supporting new use cases not in the initial design.

A cheap always on server and a hosted RDBMS are going to go a lot further for next to the same mental overhead.

[michal-stlv]

> Neat tool!

thanks! (author here not OP)

lambda/api/dynamo is just a start. I have very clear vision where i want to take this and it's not limited to lambda/api/dynamo. but these are easier to start with before you get to VPC, NAT, security groups etc. etc.

[robertlagrant]

Would love something that sets up EKS and ingress without me tearing my hair out and actually wishing I were using Azure (yikes).

[ForTheKidz]

Both of these tools hit the sweet spot starting out—good performance for cheap (not entirely true if you consider the free tier of sql services, but I've had bad experiences with those). It's the lock-in and traffic that kills you.