Pronto per #MOCA2024? Il più antico #hackercamp italiano sta arrivando!
🗓️ 13-15 settembre
📍 Torre di Cerrano - international camping
🎟️ Acquista il tuo biglietto: https://t.co/NmpaMNKb30
#workshop esclusivi
esperti del settore
attività #nerd e sfide mozzafiato
ti aspettano!!
@b0rk I'd say "don't rebase branches from which you created other branches", if others are pulling or not it's not the problem. The problem is when you have another branch totally loosing its "origin" branch history.
pushing using "--force-with-lease" it's a must when rebasing BTW.
Mountpoint for Amazon S3 – Generally Available and Ready for Production Workloads 👉 An open source file client that makes it easy for your Linux apps to connect directly to S3 buckets https://t.co/7NHLXl3poF #AWS#Storage#OpenSource
At DAZN, we had over 2M concurrent viewers at peak and crazy spiky traffic (everyone logs in 30s before a match starts).
We had a similar principle, that any service on that critical path (of a user logging in and start watching a live event) has to run on containers, because of Lambda's scaling limits.
BUT, we still have a lot of Lambda and step functions because not every part of the system have the same traffic demands. e.g. while the APIs on the critical path might see 50k rps every match day, you're more likely to see 50 rps on the payment system.
And having a microservices architecture means each team can choose the right technology.
That's one thing a lot of people have missed from this article. It's about a (probably small) part of Prime Video's system, not the whole of Prime Video.
I dunno what the Prime Video system looks like, but I bet not every part of it has such high throughput and they probably still have a lot of microservices and serverless components in there. Just not for this particular part of the system.
AND, this particular team started with serverless and it lets them go to market quickly. Then they pivoted and moved to containers when it got too expensive.
That's how you should do it! And what we have described as the "serverless-first" approach.
https://t.co/RCRIoMvlbD