3 ms·
> Tbh. As far as I can see, their data plane worked at the edge. Arguable, it's best to think of the edge as a buffering point in addition to processing. Aggr
by throwaway6920 3y ago
> Tbh. As far as I can see, their data plane worked at the edge.
Arguable, it's best to think of the edge as a buffering point in addition to processing. Aggregation has to happen somewhere, and that's where shit hit the fan.
- NicoJuicy 3y ago? That would mean their data is at the core cluster. That's not true or I haven't seen any evidence to support that statement. Cloudflare's data lives in the edge and is constantly moving. The only thing not living in the edge ( as was noticed), is stream, logpush and new image resize requests ( existing ones worked fine) from the data plane
- throwaway6920 3y ago>That would mean their data is at the core cluster. That's not true or I haven't seen any evidence to support that statement. You're being loose in your usage of 'data'. No one is talking about cached copies of an upstream, but you probably are. Read the post mortem a bit more closely. They explicitly state that the control plane(s) source of truth lives in core, and that logs aggregate back to core for analytics and service ingestion. Think through the implications on that one.
- e1g 3y agoThat’s my interpretation as well. There is one central brain, and “the edge” is like the nervous system that collects signals, sends it to the brain, and is _eventually consistent_ with instructions/config generated by the brain.