6 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
This article discusses a new Cloudflare Worker template for Vertical Microfrontends (VMFE), allowing teams to manage independent application slices based on URL paths. It explains how this architecture enables teams to own their code and deploy independently while maintaining a cohesive user experience through techniques like view transitions and preloading.
If you do, here's more
Cloudflare has introduced a Worker template for Vertical Microfrontends (VMFE), which allows multiple independent Cloudflare Workers to map to a single domain. This setup enables teams to work autonomously on different aspects of a web application—like marketing, documentation, and dashboards—without interference. Unlike traditional horizontal microfrontends that fetch components from various services, vertical microfrontends focus on ownership of specific URL paths. For instance, a team responsible for the `/blog` path maintains everything from the code to CI/CD processes for that route. This model empowers teams to deliver updates confidently, reducing the risk of regressions that often occur in monolithic code bases.
The article outlines how vertical microfrontends can create a seamless user experience, even when different teams manage separate code bases. To stitch these projects together, Cloudflare employs CSS View Transitions and document preloading. View transitions allow smooth navigation between pages, preventing the jarring white screen that often appears during page loads. By using specific CSS rules, elements like navigation bars can persist across different pages, creating the illusion of a single cohesive application. On the performance side, the Speculation Rules API lets browsers prefetch resources from interconnected vertical slices, making navigation feel nearly instantaneous.
In practical terms, this approach helps maintain a unified look and feel for users, even when underlying projects are distinct. For example, navigating between `/dash/product-a` and `/dash/product-b` can feel seamless, thanks to these techniques. The article emphasizes the importance of ensuring users remain unaware of the different code bases, as a disjointed experience could undermine the application's usability. With these strategies, teams can maintain their autonomy while delivering a coherent product to users.
Questions about this article
No questions yet.