Mysteries of Telegram Data Centers (2022)
1–10 of 166 posts
Re: Mysteries of Telegram Data Centers (2022)
#2Re: Mysteries of Telegram Data Centers (2022)
#3Why not a sticky master election per user, and have no special data centers?
Re: Mysteries of Telegram Data Centers (2022)
#4i'm far from an authority on content delivery or whatever, but the first thing I thought of was what a bizarre way to setup your infrastructure!
Re: Mysteries of Telegram Data Centers (2022)
#5This strikes me as a huge amount of custom code and technical debt. Every new software dev probably has to learn this. Why not a sticky master election per user, and have no special data centers?
Re: Mysteries of Telegram Data Centers (2022)
#6Re: Mysteries of Telegram Data Centers (2022)
#7Re: Mysteries of Telegram Data Centers (2022)
#8i'm far from an authority on content delivery or whatever, but the first thing I thought of was what a bizarre way to setup your infrastructure!
Re: Mysteries of Telegram Data Centers (2022)
#9This strikes me as a huge amount of custom code and technical debt. Every new software dev probably has to learn this. Why not a sticky master election per user, and have no special data centers?
You are suggesting to develop a compicated solution (spend money) when current simple one is working ok without any elections.
Re: Mysteries of Telegram Data Centers (2022)
#10Any DC may refuse a request and force the client to switch DC.
Profile URL doesn't show where messages/chats/channels are stored, as telegram has two dedicated DCs mostly for media. The rest DCs allow media with bandwidth being throttled.