Building vertical microfrontends on Cloudflare’s platform
Read Full ArticleSummary
The article introduces a new Worker template for Vertical Microfrontends (VMFE) on Cloudflare, allowing teams to independently manage different parts of an application by associating specific Cloudflare Workers with URL paths. This approach contrasts with traditional horizontal microfrontend architectures by enabling teams to own the entire stack for their designated routes, including frameworks, libraries, and CI/CD pipelines. The article discusses the challenges of integrating these microfrontends into a cohesive user experience and presents solutions such as CSS View Transitions and Speculation Rules to enhance navigation fluidity and performance. Additionally, it covers the implementation of a Router Worker to manage request routing and HTML rewriting for seamless integration of various microfrontends.
Key Learnings
- 1Vertical microfrontends allow teams to own entire application slices, improving autonomy and reducing regression risks.
- 2CSS View Transitions can create a unified user experience across different microfrontend projects, making navigation feel seamless.
- 3Speculation Rules can enhance performance by prefetching resources, making transitions between microfrontends feel instantaneous.
- 4A Router Worker can effectively manage request routing and HTML rewriting, ensuring that asset paths are correctly resolved for proxied requests.
Who Should Read This
Senior Frontend Engineers implementing microfrontend architectures seeking to enhance team autonomy and user experience.
Test Your Knowledge
What are the key advantages of using vertical microfrontends over traditional horizontal microfrontend architectures?
How can CSS View Transitions be implemented to enhance user experience when navigating between different microfrontends?
What challenges might arise when integrating multiple microfrontends, and how can a Router Worker address these issues?
In what scenarios would you prefer to use Speculation Rules, and how do they impact the performance of a web application?
What considerations should be taken into account when defining service bindings in a Cloudflare Worker?
Topics
More articles about Microservices
Explore Microservices engineering →You can't stream the energy: A developer's guide to Google Cloud Next '26 in Vegas
The article serves as a guide for developers attending Google Cloud Next '26 in Las Vegas, highlighting the importance of in-person collaboration and the value of hands-on learning. It outlines key...
Hyperforce Migration at Scale: How Deterministic Automation Replaced Manual Spreadsheets Across 95,000 Organizations
The article outlines the development of the Migration Intake and Processing Service (MIPS) at Salesforce, which automates the migration of over 95,000 organizations to Hyperforce. It highlights the...
Safeguarding Dynamic Configuration Changes at Scale
The article outlines Airbnb's dynamic configuration platform, Sitar, which enables safe and reliable runtime behavior changes without service interruptions. It emphasizes the importance of a coherent...
My Journey to Airbnb — Anna Sulkina
Anna Sulkina's journey to Airbnb highlights her extensive experience in engineering, particularly in application and cloud infrastructure. She transitioned from hardware diagnostics to software...
The Container paradox: Why the Inference Cloud Demands a “Decoupled” Database
The article explores the challenges of managing databases within Kubernetes clusters, particularly in the context of the Inference Cloud, where AI-driven applications require efficient data access...
More from Cloudflare Engineering
View Cloudflare engineering blogs →Complexity is a choice. SASE migrations shouldn’t take years.
The article emphasizes the shift in the cybersecurity landscape regarding SASE migrations, arguing that complexity is a choice rather than an inevitability. It showcases how Cloudflare's SASE...
Active defense: introducing a stateful vulnerability scanner for APIs
The article introduces Cloudflare's new stateful vulnerability scanner designed specifically for APIs, addressing the limitations of traditional defensive security measures. It highlights the...
Fixing request smuggling vulnerabilities in Pingora OSS deployments
The article addresses critical HTTP/1.x request smuggling vulnerabilities identified in the Pingora open source framework, particularly when deployed as an ingress proxy. It outlines the nature of...
From the endpoint to the prompt: a unified data security vision in Cloudflare One
The article outlines Cloudflare One's evolution in data security, emphasizing a unified approach that encompasses protection in transit, visibility and control at rest, and enforcement in use. It...
A QUICker SASE client: re-building Proxy Mode
The article outlines the challenges faced by security teams when implementing proxy modes in SASE environments, particularly the performance issues associated with traditional TCP implementations. It...