Bold claims like "The Prime Video team at Amazon has published a rather remarkable case study on their decision to dump their serverless, microservices architecture and replace it with a monolith instead." by DHH are just wrong and do not help the software engineering community.
My feeds on LinkedIn, Twitter, and Mastodon are full of hot takes on the Amazon Prime Blog posts. So many of them completely miss the point of what is going on. Amazon does NOT describe how they migrated Prime Video into a Monolith. They refactored one (Micro)Service.
"Now the real-world results of all this theory are finally in, and it's clear that in practice, microservices pose perhaps the biggest siren song for needlessly complicating your system." https://t.co/wWskTHStHs
In this scenario, their previous system used a micro service architecture to build one micro service part of the overall system.
The new system design refactored this one "audio/video monitoring (micro) service" to be one single system instead.
Many great presentations, lots of discussions and plenty of feedback! Our first doctoral seminar after the pandemic was a full success! A big thank you to all our group members!
The journal pre-prof of my article “Machine Learning Based Feedback on Textual Student Answers in Large Courses” with @skrusche and @bb_mountainlion is now available #OpenAccess on ScienceDirect: https://t.co/zBY9mTurd3
On average, CoFee suggested feedback for 45% of the submissions. 92% (Positive Predictive Value) of these suggestions were precise and, therefore, accepted by the instructors.
A special day for me: >22 years ago I thought we could perhaps see the supermassive black hole in the Milky Way with an earth-sized radio telescope. We calculated its appearance, colored it orange/red, coined the term 'shadow', published it, & now we see!
https://t.co/7W4tfD9Pu0