🎉 Kaizen 20 - THE ONE WHERE WE MEET - July, 2025

[gerhard]

A rough timeline of what to expect (red line is today):

gantt
    title 🎉 Kaizen 20 timeline
    dateFormat  YYYY-MM-DD
    axisFormat %b %e, %Y

    section CONTRIBUTE
    💻 ALL CONTRIBUTIONS WELCOME :2025-05-10, 77d

    section RECORD

    🎙 Record :milestone, 2025-07-26
    ✂️ Edit :2025-07-26, 6d
    🚀 SHIP IT! :milestone, 2025-08-01

    section NEXT
    Kick-off Kaizen 21 :2025-08-01, 30d

Loading

---

What changed? Kaizen.19 ... NOW

• Varnish history + setting the record straight
• Scale down the app instance size #547

---

This is a follow-up to

• ▶️ Kaizen 19 - Tip of the Pipely - May 9, 2025 #544
• ▶️ Kaizen 18 - Pipely goes BAM - Feb. 28, 2025 #538
• 🎧 Kaizen 17 - Three wise men? - Dec. 13, 2024 #525

[gerhard]

@AndrewO - Re, CDN testing: I didn’t get to actually implementing this, but years ago when I want to test how well things like expiring a cached object, change propagation, or edge functions worked in a CDN based system I was evaluating, I looked long at Jepsen.

It’s most known for testing distributed databases and I’ve never seen anyone use it to test a CDN, but IIRC it has a lot of things you’d want baked in like checking to see how long it takes for a write to be reflected in reads and what happens when you try to write while another one is still propagated.

Also, it’s really easy to spin up worldwide distributed test nodes through AWS Marketplace.

Of course you’d have to write a little bit of Clojure, but that’s what LLMs are for, right?

#friends > 92: Kaizen! Tip of the Pipely @ 💬

👆 Thanks for this great tip @AndrewO

[gerhard]

@ullgren - Putting some things straight regarding Varnish Cache, Varnish Software/Varnish+ and Fastly.

Fasly is not running Varnish+ which is Varnish Softwares product. They have their own fork that they run.

Varnish Software has their enterprise Varnish+ that companies can buy to run their own cdn at scale with alot of features that the community does not want to include.

The interesting thing here, I think, is that Varnish Cache is not under the direct control of Varnish Software. The lead developer, @bsdphk, of Varnish Cache is not employed by Varnish Software. VS are a a big contributor but it is not a setup where they 100% control the open source project.

https://www.varnish-software.com/varnish-history/

#friends > 92: Kaizen! Tip of the Pipely @ 💬

Thank you for the clarifications @ullgren. I'll make sure to set the record straight next time we record.