3 ms·

You forgot to mention IAM roles and policies. > I don't know, as an application developer, I'd rather not waste my time with stuff like that if I can avoid it.

You forgot to mention IAM roles and policies. > I don't know, as an application developer, I'd rather not waste my time with stuff like that if I can avoid it. Believe or not there are other roles besides "developer" within technology related jobs. The problem of cloud is that the heavy majority of supporters just echo the usual "scale", "maintenance" arguments without even willing to learn what those things are to the fundamental level. "You have to scale", said the developer that switch his ec2 from one type into the next, more expensive one, "now I have two vCPU, great!" And the people who knows how the real world of infrastructure is doesn't buy this cheap arguments, but are outnumbered by the louder major group. That is freaking depressing!

didibus 6y ago
> Believe or not there are other roles besides "developer" within technology related jobs I would assume much of AWS, at least the services I mentioned, are targetted at application developers though. So if you say running your own box is easier or better for running your application, you'd need to convince an application developer that it is. And as an application developer myself, like I said, I don't find it so. Targeting Lambda for example is much simpler. If I need a DB, using RDS or DynamoDB or S3 is much simpler than spinning and maintaining my own instance on my own box. If I need to publish notifications, well I don't even want to think what I'd need to do to replace SNS or SQS. If I want to have application logs and have them archived for some longer period of time, and make sure they don't fill up my box's hard drive to the max, I can just use CloudLogs. Etc. So again, you'd need to convince me it can be more convenient and less maintainance for me to use my own box instead of using those AWS services. That's even before we talk about availability and scale.

didibus 6y ago

> Believe or not there are other roles besides "developer" within technology related jobs I would assume much of AWS, at least the services I mentioned, are targetted at application developers though. So if you say running your own box is easier or better for running your application, you'd need to convince an application developer that it is. And as an application developer myself, like I said, I don't find it so. Targeting Lambda for example is much simpler. If I need a DB, using RDS or DynamoDB or S3 is much simpler than spinning and maintaining my own instance on my own box. If I need to publish notifications, well I don't even want to think what I'd need to do to replace SNS or SQS. If I want to have application logs and have them archived for some longer period of time, and make sure they don't fill up my box's hard drive to the max, I can just use CloudLogs. Etc. So again, you'd need to convince me it can be more convenient and less maintainance for me to use my own box instead of using those AWS services. That's even before we talk about availability and scale.