Serverless vs Monolith 🤔

Let's see how AWS Prime has implemented their architecture. Watch the full video to learn!

👉 Checkout codedamn on social:

If you found the video valuable, please leave a like and subscribe ❤️ It helps the channel grow and helps us push out more valuable content.

✨ Tags ✨
#aws #amazonprime #amazon #serverless #monolithsoft

[kuldeepbadhan]

Watched it on fireship few days ago. You explained really well.

[eykjbkz]

Can you make detailed video, it would be really good you explain such concepts really well.

[uditsaurabh]

Scalability, latency, cost optimisation, cpu utilisation while scaling=serverless
Serverless is any architects best tool if they can selectively use it

[thanhquachable]

thanks for an interestinf video. Regarding deployment, I used to deploy Diango on AWS( EC2, RDS...etc) - very time consuming due to steep learning curve ( it was my first time). It was great learning experience.

Now I need to prototype MVP fast, I want minimum effort deployment. On the Javascript camp, full stack NextJS seems promising, fast deploying with Vercel straight from github.

I like Python, but I want powerful UI, so django REST + React is not a bad choice. Or FastAPI + React database can be Mongo or Postgreq. But I always feel like it will take more effort to deploy these stacks comparing to the seamless NextJS Vercel.
Is it true? 😂 Thanks

[uditsaurabh]

Serverless is good where scalability and latency.

[ruchiii]

well It seems like their main bottleneck was heavy I/O network calls to and from S3 into multiple processes and thereby introducing a lot of redundencies in invoking the same data call. So it makes sense for them to merge the processes and reduce the number of I/Os.
But IMO monoliths only serve a small number of specific use cases like such. Microservices are here to stay long term(never out of fashion : )