Get ready for a game-changer! Cloudflare has just unveiled a revolutionary Worker template, and it's all about empowering decentralized teams with a unique architecture. Say hello to Vertical Microfrontends (VMFE), a path-based edge routing solution that's about to shake things up.
With VMFE, teams can now own and manage their own stacks and CI/CD pipelines, all while delivering that seamless, single-page application experience. It's like having your cake and eating it too! But here's where it gets controversial...
VMFE shifts the focus from horizontal component mixing to a vertical, path-based approach. This means that if Team A owns the /docs route, they have complete control over the entire vertical stack, from framework selection to CI/CD management, without interfering with other teams' routes. It's a bold move towards independence and specialization.
The technical magic happens through three key components. Service Bindings enable direct communication between a Router Worker and sub-application Workers at the edge, keeping latency low. The Router Worker acts as the gatekeeper, directing requests based on path prefixes. And the HTMLRewriter ensures smooth sailing by automatically fixing pathing issues, like adding /docs to image sources.
To maintain a seamless user experience, the template integrates modern browser APIs. CSS View Transitions keep DOM elements visible during page changes, eliminating that annoying white flash. Additionally, the Speculation Rules API prefetches linked microfrontends into memory, making navigation between Workers feel instantaneous (for now, only in Chromium-based browsers).
Cloudflare's own dashboard employs this model, separating core features from products like Zero Trust. As Brayden Wilmoth, a full-stack engineer at Cloudflare, explains, teams often face challenges as they grow, with different frameworks serving varying use cases. VMFE provides a solution, allowing teams to tackle complex issues like authentication and observability without the headaches of a massive migration.
While VMFE offers organizational advantages, it's not without its trade-offs. As one Reddit user pointed out, the billing model for edge-based routing can be a caveat. Adding a Router Worker means that static asset requests now hit a billable Worker first, even though the underlying static asset Workers are free. It's a trade-off that smaller teams might want to consider carefully.
Vercel, too, has seen success with a similar vertical approach, reducing preview build times significantly. However, they acknowledge the challenges, especially when it comes to local testing and certain feature workarounds. The industry is divided on this concept, with larger enterprises embracing vertical slices while smaller teams question the architectural overhead.
So, is VMFE the future of software development? Or is it a complex solution in search of a problem? What do you think? Share your thoughts in the comments and let's spark a discussion!
