Modding Apps ๐ฅ
- Subscribers
- Post coverage
- ER - engagement ratio
Data loading in progress...
Data loading in progress...
๐ณ๐Yแดแดส Nแดแดแด Sแดแดสแดs Wษชแดส๐๐ฑ๐ ๐ผ๐ข๐๐ฏ๐ค๐ฃ ๐๐ก๐๐ฅ๐ ๐๐ง๐ฉ ๐๐ค๐ค๐ค๐ฉ ๐ฟ๐๐๐ก๐จ! ๐ฑ ๐ข ๐๐๐๐ 500+ ๐๐ฟ๐๐๐ ๐พ๐๐๐๐๐๐ ๐ข ๐ ๐๐ผ๐ป'๐ ๐ง๐ผ๐๐ฐ๐ต | โ ๐๐๐ ๐ฎ๐ซ ๐๐ก๐๐ง๐ง๐๐ฅ
1500
๐๐ผ๐ ๐ฑ๐ผ๐ฒ๐ ๐๐ถ๐๐ฐ๐ผ๐ฟ๐ฑ ๐ต๐ฎ๐ป๐ฑ๐น๐ฒ ๐ฎ ๐บ๐ถ๐น๐น๐ถ๐ผ๐ป ๐ผ๐ป๐น๐ถ๐ป๐ฒ ๐๐๐ฒ๐ฟ๐ ๐ถ๐ป ๐ฎ ๐๐ถ๐ป๐ด๐น๐ฒ ๐๐ฒ๐ฟ๐๐ฒ๐ฟ? As time passed, the overall size of Discord's user base, including its most prominent communities, has grown massively. This affected servers that started to slow down and hit their throughput limits. So, they needed to scale individual Discord servers from tens of thousands to millions of concurrent users. Whenever someone sends a message on Discord or joins a channel, they need to update the date UI of everyone online on that server. They call that server a "๐ด๐๐ถ๐น๐ฑ," which runs in a ๐๐ถ๐ป๐ด๐น๐ฒ ๐๐น๐ถ๐ ๐ถ๐ฟ ๐ฝ๐ฟ๐ผ๐ฐ๐ฒ๐๐, while there is another process (a "๐๐ฒ๐๐๐ถ๐ผ๐ป") for each connected client. The guild process tracks sessions of users who are members of that guild and are responsible for actions to those sessions. When sessions get updates, forward them to the web socket socket to the client. The main issue is that ๐ฎ ๐๐ถ๐ป๐ด๐น๐ฒ ๐บ๐ฒ๐๐๐ฎ๐ด๐ฒ ๐ป๐ฒ๐ฒ๐ฑ๐ ๐๐ผ ๐ด๐ผ ๐๐ผ ๐๐ต๐ฒ ๐ป๐๐บ๐ฏ๐ฒ๐ฟ ๐ผ๐ณ ๐ฝ๐ฒ๐ผ๐ฝ๐น๐ฒ ๐ผ๐ป๐น๐ถ๐ป๐ฒ on that server, which means if a server has 1000 people online and they all send a message once, that's 1 million notifications.
3200
300
300
500
400
500
700
500
100
Your current plan allows analytics for only 5 channels. To get more, please choose a different plan.