04 of 10
Platforms
Enterprise Content Platform.
A custom CMS for a university with 2M+ daily reads. Publishing dropped from two days to fifteen minutes, and editors no longer need an engineer to push a post.
- Built at
- TechnicalBind
- Scale
- 2 Million+ daily reads.
- Category
- Platforms
- To Publish
- 15 min
- Load Time
- <50ms
Context
Every new article required a code change and a deploy. Editors waited days; engineers handled weekend pushes.
Challenge
Hand editors a self-service workflow without putting the public site at risk.
Non-negotiables
- High availability
- Multi-language support
- Fast page loads
Calls I made
- 01
Editor and reader split
Decoupled the editor from the public site. Editor downtime never reaches visitors.
- 02
Pre-rendered pages in memory
Published pages are pre-rendered and served from memory, so traffic spikes are absorbed cleanly.
Trade-offs accepted
- Optimised for readers first. The editor is functional rather than visual, while the public site is fast.
- Accepted that search takes a few minutes to update after publishing.
Outcome
Editors publish on their own, page loads dropped under 50ms, and engineering is out of the publishing loop.
Stack
- Next.js
- Django
- MySQL
- In-memory page cache
- AWS
Next.js
Django
MySQLGot something similar in mind?
Send 3 lines. I reply within a day.