3 ms·

Let’s not just pick on frontend. Has anyone seen what it takes to run something on AWS? Devops is nearing similar levels of insanity, and often for applications

Let’s not just pick on frontend. Has anyone seen what it takes to run something on AWS? Devops is nearing similar levels of insanity, and often for applications that won’t even have 50 users (seriously, all these companies that advertise for AWS experience for a tool that is going to be fucking internal with less than 50 users). It all builds up in me to be honest. You get the frontend complicated, then the deploy/infra gets complicated for the needless cloud dependency, and then the backend people don’t want to get left out of the party so they manage to rewrite their shitty php app in Go. It’s like a shitty third world country. Not only do the roads suck, but there’s no water or electricity half the time, and you need to bribe everyone to get something. Instead of it becoming a wasteland, the population somehow still increases (more people actually entering tech). Now you really can’t change anything because there’s too many people. How the wicked live.

watermelon59 6y ago
> Has anyone seen what it takes to run something on AWS? I've given up every time I've tried it on personal projects. It's just a complete poorly document mess indeed. At work we host our stuff on AWS but we have an ops team that deals with all the garbage. All I care about are APIs, endpoints and that one thing can talk to another.
- cutler 6y ago
  Yeah, so much for the fantasy of cloud platforms eliminating the need for ops staff. The guy who used to setup and manage your Linux VPSs just switched jobs to manage your AWS infra and charges extra for it.
qudat 6y ago
Finally a voice of reason. The front end isnt the only thing that has become complicated. How many services are running on k8s? Now how many of them actually need it? The list goes on. The front end isnt that complicated relative to back end, there is just one ecosystem vs 10 for the back end.
xupybd 6y ago
I recently got asked to consult for a project. I warned not to go with AWS that the tools they were wanting to put online were not well suited to AWS. Then I got sent a 15 page deployment document outlining the AWS infrastructure they had gone with. They paid megabucks and got a rube goldberg machine. To run a zend based PHP site developed 15 years ago that has never had any significant maintenance.

watermelon59 6y ago

> Has anyone seen what it takes to run something on AWS? I've given up every time I've tried it on personal projects. It's just a complete poorly document mess indeed. At work we host our stuff on AWS but we have an ops team that deals with all the garbage. All I care about are APIs, endpoints and that one thing can talk to another.

cutler 6y ago
Yeah, so much for the fantasy of cloud platforms eliminating the need for ops staff. The guy who used to setup and manage your Linux VPSs just switched jobs to manage your AWS infra and charges extra for it.

qudat 6y ago

Finally a voice of reason. The front end isnt the only thing that has become complicated. How many services are running on k8s? Now how many of them actually need it? The list goes on. The front end isnt that complicated relative to back end, there is just one ecosystem vs 10 for the back end.

xupybd 6y ago

I recently got asked to consult for a project. I warned not to go with AWS that the tools they were wanting to put online were not well suited to AWS. Then I got sent a 15 page deployment document outlining the AWS infrastructure they had gone with. They paid megabucks and got a rube goldberg machine. To run a zend based PHP site developed 15 years ago that has never had any significant maintenance.