3 ms·

>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

by hnthrow20938572 1y ago

>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.

figassis 1y ago
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?
- Voultapher 1y ago
  Many expensive big ego engineers that want to feel useful with PMs to match.
  - repeekad 1y ago
    aka what happens when you promote based on metrics rather than actual product sense
- deleted 1y ago
  [deleted]
jiggawatts 1y ago
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!
- yandie 1y ago
  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
- sandeepkd 1y ago
  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.
  - jiggawatts 1y ago
    > what other considerations were involved "DNS domains are managed by another team."

figassis 1y ago

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?

Voultapher 1y ago
Many expensive big ego engineers that want to feel useful with PMs to match.
- repeekad 1y ago
  aka what happens when you promote based on metrics rather than actual product sense
deleted 1y ago
[deleted]

jiggawatts 1y ago

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!

yandie 1y ago
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
sandeepkd 1y ago
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.
- jiggawatts 1y ago
  > what other considerations were involved "DNS domains are managed by another team."