Thanks for your Reply.
My Understanding of the CloudFlare Network is that it has several Central KV Storages.
At the Moment Pushing Dynamic Content to KV takes about 30 seconds or more to be in sync and availble worldwide.
What is needed is the Possibility to push Dynamic Changing Content and have it synced and availble in less than <= 1 second.
Technicaly this is easy to be done and Cloudflare has the possibility to do this very easy.
My Understanding is that KV Database which is very similar to the MemCached distributed IN-Memory Storage has allready a few Central Servers from which all other servers are Synced.
That way Cloudflare is able to make a fine grained Caching of its services based on request per region.
As we know not everything is stored in each Edge Node Localy.
Most data is stored only in a few central Servers around the World.
For having now the Possibility to deliver ultra fast low latency Websites with Cloudflare we need to be able to fetch Dynamic fast Chaning Content from the KV which does not require 30 Seconds or more to be Availble after the push.
To make this happen all what is needed is to have some endpoint like
where a api call can be maked from the Origin Server (best option) or a Worker (least best option as dynamic data is mostly availble on the origin server)
And this Cloudflare Endpoint hypersync.cloudflare.com
would then make a few Parallel Request to the Central KV / MemCached Servers around the World to store the small Data Chunk that changes every second and need to be displayed on the Page in parallel in a few miliseconds and make it availble by this world wide in less than 1 second.
Lets say we have as a Example a Home Page where you need show the latest loged Users or the latest Forex Prices and Forex Data which is all Dynamic only availble on the Origin Server.
This Data is not needed to be stored Atomic.
Actually we dont need Atomic Storage for majority of Data if not all of the Data that need to be Low Latency and World Wide availble.
Such a requirement would defy Physics and Natural Law !
For such a Webpage to Display fast changing Dynamic Content with Low Latency you will be making every second as a example a call from the Origin Server to the Cloudflare Endpoint hypersync.cloudflare.com over the API and send the small Chunk of the Dynamic Data to be synced worldwide in less than a Second.
The Endpoint itself upon sucess will then make 5 or 10 Parallel Request to the few Central Servers all around the World like North America, South America, Europe, Asia, Australia and send the Data to this central Servers which will make the Dynamic Data then Worldwide Availble as low latency Data close to the Suers so users in San Fracisco dont need to make anymore Requests to the Origin Servers in Europe or Asia anymore but have the Data allready very Close.
You will have the Static HTML/JS Code for this Page inside the Worker and the Dynamic Data Stored IN-Memory in the Few KV Central Servers.
The Point is making Dynamic Data Sync in less than 1 Second worldwide and be availble as Low Latency.
The 30 Seconds Delay at the Moment with KV is Bad !!!
Technically this is more than doable and i really dont understand why this is not allready solved.