2 ms·
The best use case for edge deployment is the deployment of static resources for the initial web app load. It achieves a latency of around 40ms and almost instan
by l5870uoo9y 3y ago
The best use case for edge deployment is the deployment of static resources for the initial web app load. It achieves a latency of around 40ms and almost instantly shows the user the initial render. The later database CRUD actions are much less important when the application has already loaded. Not only because much of data can be cached in the browser or aggressively pre-fetched, but also because many CRUD actions run in the background only show errors if something went wrong.
- zeroCalories 3y agoI think this depends on the application. For a complex spa, sure. But for something like a news site or social media the extra load time feels horrible. It's preferable to use server side rendering as much as possible. That also means you gotta speed up your database queries, which is where techniques like in the OP come into play.
- tracker1 3y agoEven for mostly static, edge can add a cache layer, and also do doughnut rendering for sites... By doughnut rendering, I mean you can displace certain static placeholders with user-level content... such as replacing the "login" section of the header with the markup for the User's name and profile image. These are both common use cases for Cloudflare Workers. Not just for complex compute but for near-line cache and simple transforms.