Comment on Disney+ cancellation page crashes as customers rush to quit after Kimmel suspension
DreamlandLividity@lemmy.world 5 weeks agoIf your page is just static, e.g. no login, no interaction, everyone always sees the same thing then it scales easily. Scaling means you copy the site to more servers. Now imagine a user adds a comment. Now you need to add the comment to every copy of your site, so a comment creates more work the more servers you use. And this is where scaling becomes a complex science, that you need to manually prepare for as a software developer.
BCsven@lemmy.ca 5 weeks ago
Caching 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.