3 ms·

I consider this a fallacy. I´m on the dedicated server camp, but had to use AWS in a "everything in cloud" company. I spend way more time with Lambda/Cloud for

by bratao 4y ago

I consider this a fallacy. I´m on the dedicated server camp, but had to use AWS in a "everything in cloud" company. I spend way more time with Lambda/Cloud formation/ECS shenanigans than the terraform recipe I use in dedicated servers. And this is not even considering the higher latency between services and how hard is to debug it. In your case, you are not exchanging 2 hours of a developer for a higher bill. In my experience you will get a higher bill and 5 hours of a cloud expert, and probably a solution that for every change or problem, you will have to call this expert as no one know what to do.

maerF0x0 4y ago
> the dedicated server camp, > spend way more time with Lambda/Cloud formation/ECS As you said, it's not your expertise. No one said AWS could be used well by non-experts. The point isn't the learning curve, but the terminal velocity once you get there.
nucleardog 4y ago
You could say this about... pretty much anything you're not well-versed in. Trying to use a thing that accomplishes the a similaroutcome but in a totally different way requiring a totally different skillset, it's not surprising that you found yourself needing someone who does have that skillset to assist. A Linux server guy trying to manage Windows servers will probably need help from a Windows server guy. A car driver trying to fly a Cessna somewhere will probably need help from a pilot.
jacobyoder 4y ago
FWIW, I'm in your camp mostly too. That expert may not know what to do either, or... will contradict earlier folks and say "you need to redo all of this pile..." and you'll be stuck. I've no doubt there are some workloads that really do require a level of complexity that various cloud systems offer. Much of what I've seen doesn't require it, but once someone starts down that road, they're 'justified' in learning more and tying more stuff to the cloud provider's way of doing things. I cut my teeth setting up servers back in the 90s, and that you can spin up 'full' servers (thinking various shades of VPS) in a few seconds is crazy great. But we're somehow now 'past' that... and we have mountains more complexity to consider.
frognumber 4y ago
I agree, but you're doing it wrong. I would never use Lambda, Cloud Formation, or similar. My experience with AWS is that all the original service (EC2, Route53, RDS, S3, etc.) are robust, easy, and awesome. You also avoid vendor lock-in. The massive number of proprietary newer services are junk, with the exception of some of the ML services. The ML services are sometimes helpful, but I expect they'll quickly be obsoleted.

by bratao 4y ago

maerF0x0 4y ago

> the dedicated server camp, > spend way more time with Lambda/Cloud formation/ECS As you said, it's not your expertise. No one said AWS could be used well by non-experts. The point isn't the learning curve, but the terminal velocity once you get there.

nucleardog 4y ago

You could say this about... pretty much anything you're not well-versed in. Trying to use a thing that accomplishes the a similaroutcome but in a totally different way requiring a totally different skillset, it's not surprising that you found yourself needing someone who does have that skillset to assist. A Linux server guy trying to manage Windows servers will probably need help from a Windows server guy. A car driver trying to fly a Cessna somewhere will probably need help from a pilot.

jacobyoder 4y ago

FWIW, I'm in your camp mostly too. That expert may not know what to do either, or... will contradict earlier folks and say "you need to redo all of this pile..." and you'll be stuck. I've no doubt there are some workloads that really do require a level of complexity that various cloud systems offer. Much of what I've seen doesn't require it, but once someone starts down that road, they're 'justified' in learning more and tying more stuff to the cloud provider's way of doing things. I cut my teeth setting up servers back in the 90s, and that you can spin up 'full' servers (thinking various shades of VPS) in a few seconds is crazy great. But we're somehow now 'past' that... and we have mountains more complexity to consider.

frognumber 4y ago

I agree, but you're doing it wrong. I would never use Lambda, Cloud Formation, or similar. My experience with AWS is that all the original service (EC2, Route53, RDS, S3, etc.) are robust, easy, and awesome. You also avoid vendor lock-in. The massive number of proprietary newer services are junk, with the exception of some of the ML services. The ML services are sometimes helpful, but I expect they'll quickly be obsoleted.