Re:To Cover China, There’s No Substitute for WeChat
by hero76 on Friday January 18, 2019 @01:38PM
(#18941599)
here is an article in english of wechats architecture
https://blog.acolyer.org/2018/11/16/overload-control-for-sca...
Re:To Cover China, There’s No Substitute for WeChat
by azurezyq on Friday January 18, 2019 @01:23PM
(#18941459)
Actually they shared a lot but vast majority of them in Chinese.
Re:To Cover China, There’s No Substitute for WeChat
by yorwba on Friday January 18, 2019 @02:39PM
(#18942243)
Could you link to some Chinese-language resources they published?
Re:To Cover China, There’s No Substitute for WeChat
by azurezyq on Friday January 18, 2019 @03:00PM
(#18942456)
Just did a brief search and found a few links:
https://www.infoq.cn/article/the-road-of-the-growth-weixin-b...
https://cloud.tencent.com/developer/article/1005631
There seems more on cloud.tencent.com/developer.
And you can check their presentations on major per-field conferences like AI or big data or something.
Re:To Cover China, There’s No Substitute for WeChat
by faitswulff on Friday January 18, 2019 @01:37PM
(#18941595)
Turnabout for an industry dominated by English.
Re:To Cover China, There’s No Substitute for WeChat
by justicezyx on Friday January 18, 2019 @01:42PM
(#18941657)
Well, if you used the app, you'll see that these components are largely independent.
IMHO, architecture wise, they are not particularly interesting.
Re:To Cover China, There’s No Substitute for WeChat
by cakeface on Friday January 18, 2019 @02:36PM
(#18942222)
We're looking at their Tinker[1] open source library for hot patching Android apps. They seem to have quite a few other projects on Github.
Re:To Cover China, There’s No Substitute for WeChat
by omouse on Friday January 18, 2019 @10:22PM
(#18945121)
>. With their massive amount of users and incredibly diverse service offerings I'd love to see their backend architecture design choices/tradeoffs.
Probably helps when the govt is footing at least part of the bill in order to access tons of data and information ;-)
It's unfortunate not much of their architecture is publicly shared or discussed. With their massive amount of users and incredibly diverse service offerings I'd love to see their backend architecture design choices/tradeoffs.