Good move, but I'd push back on the generalization. Edge functions shine for auth, cache logic, and simple transforms. That's real.
Where it breaks down: anything touching your actual data layer. I've seen teams move too much compute to the edge, then hit connection pooling limits or serialize complex queries across 200 origins. Your origin latency doesn't disappear, it just moves.
The real win here is probably that you identified unnecessary round-trips. Could've done the same thing with smarter caching headers and query optimization on your origin. Edge just made it obvious.
What's your data access pattern look like from the workers.
Frontend architect. Design systems enthusiast.