3 ms·

You either completely missed the point or you are too invested in going off on a tangent to try to change the subject. The $100 vs $10 was not intended to argu

You either completely missed the point or you are too invested in going off on a tangent to try to change the subject. The $100 vs $10 was not intended to argument the merit of $10 savings: it refutes the absurd claim that $100 expenditures justifies adopting a convoluted architecture, because the fact is not adopting a convoluted architecture is actually much cheaper. Additionally, somehow you've brushed aside the fact that the main cost is developer time, and a convoluted solution based on flavor-of-the-month tech fads requires more maintenance and developer man-hours than basic tried-and-true solutions like standard run-of-the-mill web services. > How much would it cost to have build servers that could handle peak demand and how much of a waste would it be to have that server sitting idle? I honestly fail to see what point you're trying to make because: a) you don't need "serverless" services such as AWS lambdas to get CICD pipelines to work, and b) cluster autoscaling is a basic offering provided by pretty much all major cloud providers. Thus, what's your point? > As far as it taking “two or three weeks” - “its a poor craftsmen who blames his tools”. So any proof that refutes your baseless assertions is brushed aside by your "you're holding it wrong" baseless assertion? Doesn't sound like a discussion on technical merits. You're underlining the biggest problem with buzzword-driven development: the lack of technical merit is a constant and everything boils down to petty personal politics.

scarface74 7y ago
Your “proof” is an anecdote that was easily disproven by a link. If it takes your developers two weeks to host an API in a Lambda when I showed you a link on how simple it is. It says more about your developers than AWS. My time is far from cheap and any time that we can spend letting someone else do the grunt work is valuable.
- rumanator 7y ago
  > Your “proof” is an anecdote that was easily disproven by a link. Real-world problems don't go away when you try to brush them aside. You either face the facts or remain in fantasy land. > If it takes your developers two weeks to host an API in a Lambda Please don't put words in other people's mouths. You have absolutely no idea about what the problems were and already made it quite clear that you don't care about facts or reality, and simply prefer to fabricate accusations to avoid discussing technical issues. That speaks volumes about your own competence and technical ability.
  - scarface74 7y ago
    I’m going by the only facts that you offered. You said that it took your developers two weeks to do something that should only take an hour. I showed you an example of how to host a standard API or website within lambda with minimum effort. If your developer haven’t come up with processes to efficiently manage their development and deployment processes - it’s a process issue that others have already solved.
    - rumanator 7y ago
      > I’m going by the only facts that you offered. You did not. You fabricated accusations to fill gaps in your comprehension based on your imagination alone, and proceeded to use your made-up accusations to attack others. That's not cool, and just speaks volumes regarding your lack of arguments and your ability to contribute to a discussion.
      - scarface74 7y ago
        Your comment I have first-hand accounts of how FaaS offerings have lead developers to waste a couple of weeks getting FaaS to do what could have been done in a couple of hours with a tried-and-true web service. There is no world where a competent developer who knows his tooling should take “a couple of weeks” to set up an API on lambda that would only take “a couple of hours on a web server”. You can treat a lambda instance just like a web server by using API Gateway, proxy integration and simple to use function provided by AWS that translates the lambda/APIGW event to a form that your framework expects. Hosting static content on S3 (css, JS, html) is a click of a few buttons. Copying your content is a simple “aws s3 cp” command to do an “xcopy deployment”.

scarface74 7y ago

Your “proof” is an anecdote that was easily disproven by a link. If it takes your developers two weeks to host an API in a Lambda when I showed you a link on how simple it is. It says more about your developers than AWS. My time is far from cheap and any time that we can spend letting someone else do the grunt work is valuable.

rumanator 7y ago
> Your “proof” is an anecdote that was easily disproven by a link. Real-world problems don't go away when you try to brush them aside. You either face the facts or remain in fantasy land. > If it takes your developers two weeks to host an API in a Lambda Please don't put words in other people's mouths. You have absolutely no idea about what the problems were and already made it quite clear that you don't care about facts or reality, and simply prefer to fabricate accusations to avoid discussing technical issues. That speaks volumes about your own competence and technical ability.
- scarface74 7y ago
  I’m going by the only facts that you offered. You said that it took your developers two weeks to do something that should only take an hour. I showed you an example of how to host a standard API or website within lambda with minimum effort. If your developer haven’t come up with processes to efficiently manage their development and deployment processes - it’s a process issue that others have already solved.
  - rumanator 7y ago
    > I’m going by the only facts that you offered. You did not. You fabricated accusations to fill gaps in your comprehension based on your imagination alone, and proceeded to use your made-up accusations to attack others. That's not cool, and just speaks volumes regarding your lack of arguments and your ability to contribute to a discussion.
    - scarface74 7y ago
      Your comment I have first-hand accounts of how FaaS offerings have lead developers to waste a couple of weeks getting FaaS to do what could have been done in a couple of hours with a tried-and-true web service. There is no world where a competent developer who knows his tooling should take “a couple of weeks” to set up an API on lambda that would only take “a couple of hours on a web server”. You can treat a lambda instance just like a web server by using API Gateway, proxy integration and simple to use function provided by AWS that translates the lambda/APIGW event to a form that your framework expects. Hosting static content on S3 (css, JS, html) is a click of a few buttons. Copying your content is a simple “aws s3 cp” command to do an “xcopy deployment”.