Re:A million-dollar engineering problem
by nulagrithom on Friday March 17, 2017 @11:00AM
(#13894433)
> before you go full-hog on AWS, do some simple math first
I had a coworker who was turned off of AWS by clicking the "Dedicated IP" checkbox when deploying a CloudFlare distribution with SSL.
One month and $600[0] later he swears up and down that AWS is the devil.
You can spend an amazing amount of money on AWS by accident and/or without need. Hourly pricing is a huge footgun. Best to run everything through the "Simple" Monthly Calculator: https://calculator.s3.amazonaws.com/index.html
Weeks of work can save hours of meetings.
Re:A million-dollar engineering problem
by thecrazyone on Friday March 17, 2017 @03:34PM
(#13897236)
interesting thing to say, but did you plan for it to mean something in this context? :)
Nothing special - just the whole "Yeah, saw your email† ... look, I'm so busy, did you get the site up and running again? I'll get back to you on this after my vacation" management style which seems to drive a great many "decisions" that are made in this realm. And on which AWS, implicitly, banks a great deal of its business model on.
† About the monthly you-know-what bill now well into 5 figures, and climbing.
> At this point simply not using AWS is a competitive advantage.
Re:A million-dollar engineering problem
by logfromblammo on Thursday March 16, 2017 @10:12PM
(#13890822)
I read this as suggesting that a simple arbitrary rule to not use AWS is likely to save both money and also the time that would otherwise be spent tuning your use of AWS to cost less money.
Your time is valuable too. It could be spent developing something novel instead of messing around with server configuration.
But that's not what the commenter was saying, of course.
More like (paraphrasing) "before you go full-hog on AWS, do some simple math first." Which an amazingly high percentage of people neglect to do, these days.