3 ms·

Same with the whole "serverless" thing heavily pushed by Amazon and co which conveniently offer "serveless services". These trends are always pushed by marketin

Same with the whole "serverless" thing heavily pushed by Amazon and co which conveniently offer "serveless services". These trends are always pushed by marketing departments at SAAS companies.

simplotek 4y ago
> Same with the whole "serverless" thing heavily pushed by Amazon and co which conveniently offer "serveless services". These trends are always pushed by marketing departments at SAAS companies. This take is pure nonsense. It's highly disappointing to see this blend of ignorant and uninformed take in HN of all places. Amazon's serverless offerings are the ideal tool for many use cases, specially internal services. Instead of being forced to write, deploy, operate and maintain a dedicated service to handle events, just write the event handlers you need, get it to run in someone else's computer, and forget about it. Internally, things like AWS Lambda saves a lot on wasted allocated capacity. You don't need to waste allocating a whole box to run a handler each time, say, someone uploads a file to S3.
jasfi 4y ago
Microservices are an option, serverless is an option. Use the right tool for the job as much as is required, but don't overdo something that causes unnecessary excessive maintenance.
- throw_m239339 4y ago
  > Microservices are an option, serverless is an option. Use the right tool for the job. Developers don't need these "tools" pushed by marketing departments at first place. These aren't technical solutions, these are marketing considerations, solutions looking for a problem AKA "hype driven development".
- Tomis02 4y ago
  > Use the right tool for the job When losing an argument, some people resort to the "it's just a tool, use the right tool for the job" cop-out instead of admitting it's a bad tool and moving on. I don't think it's a good argument at all. It's a phrase you can use to defend anything.
lupire 4y ago
Amazon did it for themselves first.

Same with the whole "serverless" thing heavily pushed by Amazon and co which conveniently offer "serveless services". These trends are always pushed by marketing departments at SAAS companies.

simplotek 4y ago

> Same with the whole "serverless" thing heavily pushed by Amazon and co which conveniently offer "serveless services". These trends are always pushed by marketing departments at SAAS companies. This take is pure nonsense. It's highly disappointing to see this blend of ignorant and uninformed take in HN of all places. Amazon's serverless offerings are the ideal tool for many use cases, specially internal services. Instead of being forced to write, deploy, operate and maintain a dedicated service to handle events, just write the event handlers you need, get it to run in someone else's computer, and forget about it. Internally, things like AWS Lambda saves a lot on wasted allocated capacity. You don't need to waste allocating a whole box to run a handler each time, say, someone uploads a file to S3.

jasfi 4y ago

Microservices are an option, serverless is an option. Use the right tool for the job as much as is required, but don't overdo something that causes unnecessary excessive maintenance.

throw_m239339 4y ago
> Microservices are an option, serverless is an option. Use the right tool for the job. Developers don't need these "tools" pushed by marketing departments at first place. These aren't technical solutions, these are marketing considerations, solutions looking for a problem AKA "hype driven development".
Tomis02 4y ago
> Use the right tool for the job When losing an argument, some people resort to the "it's just a tool, use the right tool for the job" cop-out instead of admitting it's a bad tool and moving on. I don't think it's a good argument at all. It's a phrase you can use to defend anything.

lupire 4y ago

Amazon did it for themselves first.