Uploaded March 2025 | Updated September 2026, 2 weeks ago
Namespace.so was born from the need to run lots of tests efficiently, across a large amount of on-demand compute that spins up in seconds, and scales back down to 0.
Hugo Santos shows us Foundation, an open-source Kubernetes application platform that powers Namespace's developer-optimized compute platform. We see a testing framework that has a:
- Service-Oriented Architecture: The system manages how services are written, built, tested, deployed, and monitored in production
- Container-Centric Approach: Everything runs in containers within Kubernetes clusters
- Fast Test Execution: Tests that would normally be slow are dramatically accelerated through parallelization
- Complete Isolation: Each test runs in its own dedicated Kubernetes cluster for complete isolation
TECHNICAL INFRASTRUCTURE:
1. Kubernetes Distribution: Uses customized k3s for speed
2. Container Runtime: Custom-managed ContainerD (version 1.7)
3. Operating System: Wolfi-based with custom kernel (6.7)
4. Deployment Speed: New Kubernetes clusters become ready in under 2 seconds
5. Scale: Can easily manage dozens of parallel test environments
If you want to watch the full conversation, as a 4k movie, go to πΊ makeitwork.tv/fast-infrastructure and join as a member.
Alternatively, you can listen to the conversation at π§ https://makeitwork.fm/12
There are 2 other videos that go well with this one:
youtube.com/watch?v=zDJ-EE1f82w
youtube.com/watch?v=BSD-E8I7JNE
Namespace.so was born from the need to run lots of tests efficiently, across a large amount of on-demand compute that spins up in seconds, and scales back down to 0.
Hugo Santos shows us Foundation, an open-source Kubernetes application platform that powers Namespace's developer-optimized compute platform. We see a testing framework that has a:
- Service-Oriented Architecture: The system manages how services are written, built, tested, deployed, and monitored in production
- Container-Centric Approach: Everything runs in containers within Kubernetes clusters
- Fast Test Execution: Tests that would normally be slow are dramatically accelerated through parallelization
- Complete Isolation: Each test runs in its own dedicated Kubernetes cluster for complete isolation
TECHNICAL INFRASTRUCTURE:
1. Kubernetes Distribution: Uses customized k3s for speed
2. Container Runtime: Custom-managed ContainerD (version 1.7)
3. Operating System: Wolfi-based with custom kernel (6.7)
4. Deployment Speed: New Kubernetes clusters become ready in under 2 seconds
5. Scale: Can easily manage dozens of parallel test environments
If you want to watch the full conversation, as a 4k movie, go to πΊ makeitwork.tv/fast-infrastructure and join as a member.
Alternatively, you can listen to the conversation at π§ https://makeitwork.fm/12
There are 2 other videos that go well with this one:
youtube.com/watch?v=zDJ-EE1f82w
youtube.com/watch?v=BSD-E8I7JNE







![CDN PURGE with Elixir
https://makeitwork.tv π full version shipping any week now
We implement the following one-liner bash script the Elixir Wayβ’:
dig cdn-2025-02-25.internal AAAA +short | while read ipv6; do curl -so /dev/null -w %{http_code} %{method} %{url_effective}n -X PURGE http://[$ipv6]:9000/; done
Find the code and the conversation in this pull request π https://github.com/thechangelog/changelog.com/pull/549
π€ THE PROBLEM: CDN is serving stale content, with some entries expired for over 4 minutes. We need a way to explicitly purge cache across all CDN instances rather than waiting for user requests to trigger refreshes.
πββοΈ THE SOLUTION: DNS lookups to discover all instances and coordinate purges across them.
π§βπ§ THE DNS THING (02:26): Using Fly.ios internal DNS system, we implement IPv6 lookups to discover all CDN instances. Claude Code helps. It works the first time π
π BUGS & PREDATORS (3:00): Undefined function errors, mock testing issues, and the classic double-slash URL bug. No Claude Code, just experience.
π§ DID IT WORK? (6:56): Lets force push straight into production and see what happens π±
This session isnt just a tutorial - its an authentic look at collaborative coding, where DNS magic meets Elixir elegance to conquer distributed caching.
If youre into DevOps, CDNs, or just love seeing bugs squashed in real time, this gives you the tools to understand (and maybe implement) your own purge system.
00:00 The Problem
00:46 The Solution
02:26 The DNS thing
03:00 Bugs & Predators
04:43 Lets fire this up
06:56 Lets force push it
07:25 Is it working?
08:53 No no no CDN PURGE with Elixir](https://i.ytimg.com/vi/fhQd9XaZTr8/mqdefault.jpg)


