Netflix Ditched Kafka for THIS in CQRS

Netflix recently rebuilt Tudum by rethinking their CQRS implementation. They moved away from Kafka and Cassandra to a new in-memory approach using RAW Hollow. Let me break down what their architecture and clear up a few misconceptions about CQRS, what it really means (and what it doesn’t), why Netflix made this change, and the key lessons you can apply to your own systems. 🔗 Kurrent (formely EventStoreDB) https://kurrent.io 🔔 Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmation=1 💥 Join this channel to get access to a private Discord Server and any source code in my videos. 🔥 Join via Patreon https://www.patreon.com/codeopinion ✔️ Join via YouTube https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join 📝 Blog: https://codeopinion.com 👋 Twitter: https://twitter.com/codeopinion ✨ LinkedIn: https://www.linkedin.com/in/dcomartin/ 📧 Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeopinion 0:00 Existing Architecture 3:27 Typical Implementation 4:43 Mi