[DiscordArchive] also splitting it is nice but would there be only 1 of each ?
[DiscordArchive] also splitting it is nice but would there be only 1 of each ?
Archived author: Rymercyble • Posted: 2023-07-13T16:25:01.404000+00:00
Original source
also splitting it is nice but would there be only 1 of each ?
Archived author: Foe • Posted: 2023-07-13T16:26:12.528000+00:00
Original source
For some of the services it doesn't make sense to have an active/active design, but you could feasibly do active/standby for most services
Archived author: Rymercyble • Posted: 2023-07-13T16:26:53.925000+00:00
Original source
im just thinking that if doing something like this it wouldnt be bad to keep in mind option to have at least 2 of each in case 1 crashes
Archived author: Foe • Posted: 2023-07-13T16:27:59.866000+00:00
Original source
Yeah, that would be active/standby for most cases, for things like the map services you'd probably not get away with that, but you'd have multiple map services, each dedicated to specific maps
Archived author: Foe • Posted: 2023-07-13T16:28:16.993000+00:00
Original source
More for load balancing than redundancy
Archived author: Rymercyble • Posted: 2023-07-13T16:29:15.083000+00:00
Original source
also would it be 1 chat service for all realms ? i remember cases from retail where somewhere some chat was working and some not
Archived author: Foe • Posted: 2023-07-13T16:29:54.781000+00:00
Original source
I would go by that design personally, it's a lot cleaner to have one service handle it, than the map service handling some, one service handling guild chat, one service handling party chat etc
Archived author: Foe • Posted: 2023-07-13T16:30:38.764000+00:00
Original source
From a load perspective there's no real reason to split those functions, and you could have a hot/cold design. So if chat server 1 dies, chat server 2 takes over almost immediately
Archived author: Foe • Posted: 2023-07-13T16:31:48.589000+00:00
Original source
Not like they really have to consider context for anything, so you could always round-robin across those two services, but I'd much rather have a hot/cold design from a management and maintenance perspective
Archived author: Foe • Posted: 2023-07-13T16:32:18.696000+00:00
Original source
You could patch Chat2, then migrate master to Chat2, shut down Chat1 and patch that one with no loss in chat functionality