From our perspective I'm not sure the cloud abstraction is better or we even want it to be done like that locally. Look at S3 as an API for example. It's absolutely dire. I'd rather use NFS (!). And stuff like Lambda and Cloud Functions are just cat turds.

On the DB side, I can't say too much as we're a pretty obviously identifiable AWS customer if I give out any details. I will only say that nothing fits our size and scale so we have to run on bare metal. That just makes it really fucking expensive colocation.

▲

AllanSavageDev 2 hours ago | parent [-]

Lambda is awesome .. until you actually try to use it for realsies. Cat turd is an apt description. Just being able to get the damn logs for debugging is itself a hassle. Terraform helps a ton in all this and I rarely find myself using the AWS UI anymore. Still Lambda is a great idea that just doesn't deliver for any use case more than responding to some S3 upload action or Event Bridge operation.

Don't even get me started on the API Gateway sitting in front of a group of related Lambdas. Its OK once you get it setup and running but buildign/changing it amounts to stabbing yourself in the eyes.

	▲	OhMeadhbh 19 minutes ago \| parent \| next [-]
		I saw you post "lambda is awesome" and was going to reply with "only in certain circumstances." But you beat me to it. After about a year of poking lambda to see how it actually worked (versus how it was documented) and building a cloud formation replacement (TF eventually did what I wanted, but not before I made a simple PROLOG based replacement for it). But I finally made it work after MUCH struggle. So... +1. I put this in our code several years ago: "WARNING: Do not look at Lambda stack with remaining eye."
	▲	meekins 5 minutes ago \| parent \| prev [-]
		[dead]