@iamtheV0RTEX

"Self hosted vs serverless" and "monolith vs microservices" are independent axes. If you put your entire application logic into a single container that you run using App Runner, that's a serverless monolith. If you build your app as a fleet of microservice containers but you run them on your own hardware, that's self-hosted microservices.

@MosiurRahman-dl5ts

Tom is a genius, he could've scaled it much better.

@holistic_cto

"that doesn't look like a high school project" 💀 I'm a frontend engineer at Amazon and this is so true. There is no culture of frontend development at Amazon

@rubyh4184

The key of designing system that could scale horizontally is Stateless. Monolith could scale horizontally as long as the instances are stateless. The answer was never always microservice to scale horizontally.

@Ivan26t

Amazon needs to hire UX designers and front-end developers. Amazon's website was built by a backend developer 😅

@onee1594

Problem was not serverless and not even microservices. 
Problem was bad design

@DeusExAstra

I think if you just run your micro services on Subversion, that would solve all your problems.  Also, Tom is a genius.

@martg0

Serverless is ok depending on the use case, not for everything. I’ve done migrations and switched from a 3500 USD/mo bill using ec2, and RDS to less than 100USD/mo using nextjs running on lambdas + DynamoDB + Cloudfront

@TECHN01200

It kinda makes sense, you don't pay the internet bill if you don't transfer anything over the internet.

@yuriib5483

our devs recently accrued 200k spend on cloudwatch, over weekend, after Friday dev branch change because they looped lambda calling itself and their code had verbose logging. with 10mil monthly spend it is drop in a bucket but for small org that's be end of company. most dinosaurs of development don't understand cloud infra and cost pillar well enough to be doing serverless

@IvanRandomDude

Tom can fix serverless

@OBGynKenobi

Pretty soon we'll all be programming in assembly again.

@TechBuddy_

Tom is a genius

@ninjaasmoke

ugh aws lambdas are just ugh.
i recently joined a company that has a micro service’s architecture built with around 1000+ lambdas. each doing different things. 

for each, we have asked aws to allow upto 20k concurrent requests. now we are supposed to handle over 40k as our company’s growing. and the time AWS takes to scale the lambda is over 30minutes!?? we are switching to kubernetes jobs as an alternative.

and now i’ve to rewrite code for 1k lambdas 🙂

@leaxical

The world is not ready for serverless JDSL.

@Alex-hr2df

The best solution is to adopt a hybrid approach that combines serverless and monolithic architectures. Critical components benefit from serverless scalability, while less dynamic parts are consolidated into a monolith. This maximizes resource utilization, cost efficiency, and flexibility in scaling. Continuous monitoring and optimization ensure a cost-effective and scalable solution.

@jefffriedman6942

"You'll compute nothing and you'll be happy" - LOL

@dmitriylevy7865

3:35 that laughter is legendary

@wlockuz4467

The main point is that Amazon Prime was doing something thats inherently impossible with Serverless and thats how they save 90% by moving away from it.

@chrisE815

"Someone call a data scientist in here immediately." Said no one trying to get something important done...