Comment on Disney+ cancellation page crashes as customers rush to quit after Kimmel suspension
BCsven@lemmy.ca 5 weeks agoCaching servers, they self replicate when a change is committed, then send back a signal to main server that task has completed
DreamlandLividity@lemmy.world 5 weeks ago
I am not sure what you are trying to say?
BCsven@lemmy.ca 5 weeks ago
Oh right, I skipped a part. It is not really a dev complexity prep issue. You build the database that serves the comments etc in as of in one place, then you deploy cache servers for scaling. They self replicate, so a comment in California gets commited to the dbase, the server in new York pulls the info over from the Cali change, it sends back that it is synced with the change. And vice versa. The caching servers do the work, not your program.
DreamlandLividity@lemmy.world 5 weeks ago
That entirely depends on your application. What you described is one possible approach, that will only work in specific circumstances.
BCsven@lemmy.ca 5 weeks ago
Besides application specifics, its how the internet works currently to give low latency. AWS, Azure, Linode etc have data centers across the globe to replicate data near where the people are.