News for hackers. Stuff that matters.

A comment on Netflix Revamps Tudum's CQRS Architecture with Raw Hollow In-Memory Object Store.

Re:Netflix Revamps Tudum's CQRS Architecture with Raw Hollow... by hnthrow20938572 on Tuesday August 19, 2025 @05:25AM (#44949773)
>However, due to the caching refresh cycle, CMS updates were taking many seconds to show up on the website. The issue made it problematic for content editors to preview their modifications and got progressively worse as the amount of content grew, resulting in delays lasting tens of seconds.

This seems superficial, why not have a local-only CMS site to preview changes for the fast feedback loop and then you only have to dump the text to prod?

>got progressively worse as the amount of content grew, resulting in delays lasting tens of seconds.

This is like the only legit concern to justify redoing this, but even then, it was still only taking seconds to a minute.

[ Parent | on HN ]
Re:Netflix Revamps Tudum's CQRS Architecture with Raw Hollow... by figassis on Tuesday August 19, 2025 @06:23AM (#44950046)
Was just about to say this. There are many local first, open source CMSs and so the cost to customize them (or just build a plugin) to edit locally and publish remotely would be way less that this infra. What am I missing?
[ Parent | on HN ]
Re:Netflix Revamps Tudum's CQRS Architecture with Raw Hollow... by Voultapher on Tuesday August 19, 2025 @10:22AM (#44951882)
Many expensive big ego engineers that want to feel useful with PMs to match.
[ Parent | on HN ]
Re:Netflix Revamps Tudum's CQRS Architecture with Raw Hollow... by repeekad on Tuesday August 19, 2025 @10:54AM (#44952264)
aka what happens when you promote based on metrics rather than actual product sense
[ Parent | on HN ]
Re:Netflix Revamps Tudum's CQRS Architecture with Raw Hollow... by jiggawatts on Tuesday August 19, 2025 @09:16AM (#44951155)
The common solution is to spin up a dedicated DNS hostname called something like "preview.www.netflix.com" and turn off all caching when users go via that path. Editors and reviewers use that, and that's... it. Solved!
[ Parent | on HN ]
Re:Netflix Revamps Tudum's CQRS Architecture with Raw Hollow... by sandeepkd on Tuesday August 19, 2025 @12:18PM (#44953281)
A solution as simple as this is not easy to miss, on other side, to be fair its hard to know what other considerations were involved in the review and design process. Some one had to present a reasonable rationale to go in a certain direction.
[ Parent | on HN ]
Re:Netflix Revamps Tudum's CQRS Architecture with Raw Hollow... by jiggawatts on Tuesday August 19, 2025 @05:35PM (#44956475)
> what other considerations were involved

"DNS domains are managed by another team."

[ Parent | on HN ]
Re:Netflix Revamps Tudum's CQRS Architecture with Raw Hollow... by yandie on Tuesday August 19, 2025 @12:15PM (#44953250)
But I need to build a beautiful system with global scale!!

They inflated the problem of “make content preview faster” for a small number of users to “make a fast global cache system”. That’s promotion material for you

[ Parent | on HN ]