<story><title>Scaling up the Prime Video audio/video monitoring service and reducing costs</title><url>https://www.primevideotech.com/video-streaming/scaling-up-the-prime-video-audio-video-monitoring-service-and-reducing-costs-by-90</url></story><parent_chain><item><author>boredumb</author><text>AWS has a great business model of people over &amp;quot;optimizing&amp;quot; their architecture using new toys from amazon and being charged through the nose for it. It&amp;#x27;s amazing how clients that are doing a few requests per second will want a fully distributed, serverless, microservice + dynamodb + s3 + athena + etc + etc, in order to serve a semi-static web app and print some reports off throughout the day and pay 10-50k a month when the entire thing could run on a few nodes and even a managed RDS instance for a thousand bucks a month. I would argue at this point that early optimization of architecture is astronomically worse than even* your co-worker that keeps turning all of your non-critical, low-volume iterable functions into lanes to utilize SIMD instructions.&lt;p&gt;Some irony in my anecdotal experiences is that most places that don&amp;#x27;t have the traffic to justify the cost of these super distributed service architectures also see a performance penalty from introducing network calls and marshaling costs</text></item></parent_chain><comment><author>steveBK123</author><text>Yes, and it attracts just the wrong kind of dev&amp;#x2F;architects.
At a previous shop, we hired a cloud architect to drive our &amp;quot;cloud adoption&amp;quot;.
He of course bet the farm on a set of new AWS services that were barely in version v0.9 to be the backbone of the system he architected.&lt;p&gt;It quickly became clear even he had no experience with the set of tools &amp;amp; services he had advocated, and the whole thing went off the rails slowly &amp;amp; surely.&lt;p&gt;Low &amp;amp; behold 100% of existing customers are still on the on-prem offering 2 years later, and if you throw in the new customers that were shoehorned onto the AWS offering, his team has captured 2% of customer use after 2 years of effort.</text></comment>
<story><title>Scaling up the Prime Video audio/video monitoring service and reducing costs</title><url>https://www.primevideotech.com/video-streaming/scaling-up-the-prime-video-audio-video-monitoring-service-and-reducing-costs-by-90</url></story><parent_chain><item><author>boredumb</author><text>AWS has a great business model of people over &amp;quot;optimizing&amp;quot; their architecture using new toys from amazon and being charged through the nose for it. It&amp;#x27;s amazing how clients that are doing a few requests per second will want a fully distributed, serverless, microservice + dynamodb + s3 + athena + etc + etc, in order to serve a semi-static web app and print some reports off throughout the day and pay 10-50k a month when the entire thing could run on a few nodes and even a managed RDS instance for a thousand bucks a month. I would argue at this point that early optimization of architecture is astronomically worse than even* your co-worker that keeps turning all of your non-critical, low-volume iterable functions into lanes to utilize SIMD instructions.&lt;p&gt;Some irony in my anecdotal experiences is that most places that don&amp;#x27;t have the traffic to justify the cost of these super distributed service architectures also see a performance penalty from introducing network calls and marshaling costs</text></item></parent_chain><comment><author>abluecloud</author><text>It&amp;#x27;s honestly like a cult and a desire to want to &amp;quot;do it right&amp;quot; on AWS. The last few projects I&amp;#x27;ve spent so much time setting up code deploy, load balancers, certificates, SES, route 53... This newest project, I&amp;#x27;ve gone to heroku with everything being basically a few clicks to get setup.</text></comment>