Incremental adoption of micro-frontends ...
I just came across this recent Cloudflare blog post talking about Fragment Piercing. It seems like quite a useful approach for improving a legacy application, but one thing isn't quite clear to me - how do you implement the Piercing Gateway Worker? Specifically, how does the browser know to point to the Piercing Gateway Worker rather than the Legacy Application host/server? Is there a way to point a domain's DNS to a specific CF Worker? Until I found this post, my plan was to just use Workers in conjunction with a client-side Service Worker to intercept requests and manipulate them as necessary.
https://blog.cloudflare.com/fragment-piercing/
The Cloudflare Blog
Incremental adoption of micro-frontends with Cloudflare Workers
With Cloudflare Workers, our fragment-based micro-frontend architecture, and fragment piercing technique, engineering teams can incrementally improve large frontends in a fraction of the time, yielding significant user and developer experience gains.
1 Reply
Nevermind. I see that there's lots of options related to this
https://developers.cloudflare.com/workers/learning/how-routing-works/
https://developers.cloudflare.com/workers/platform/triggers/routes/
https://developers.cloudflare.com/workers/platform/triggers/custom-domains/
How routing works · Cloudflare Workers docs
Documentation for Cloudflare Workers, a serverless execution environment that allows you to create entirely new applications or augment existing ones without configuring or maintaining infrastructure.
Routes · Cloudflare Workers docs
Documentation for Cloudflare Workers, a serverless execution environment that allows you to create entirely new applications or augment existing ones without configuring or maintaining infrastructure.
Custom Domains · Cloudflare Workers docs
Documentation for Cloudflare Workers, a serverless execution environment that allows you to create entirely new applications or augment existing ones without configuring or maintaining infrastructure.