Sharing random thoughts~
2023的必然不会很冗长，尤其是工作上的进展在前一篇文章已经总结过了，2023 对于我来说其实可以用平淡来形容，其中仍然有一些确幸。这一年给自己打 80 分，比去年高一些，因为做出了一些改变，值得比去年高十分。
The weekend started as any other, but it quickly took an unusual turn when our users reported a bizarre issue on our chat page. As the backend developer for the Instant Messaging (IM) Team, I found myself bombarded with feedback indicating that the chat page was displaying strange languages.
I used to share my understanding and architecture of the Google File System. Today I will share Bigtable, a revolutionary distributed database build upon GFS by Google
Distributed database / file system is crucial for understanding how our distributed system works. During the progression of all DB/ File systems. Google File System lays the foundation for a massive scalable system. So I would love to share this classic design and if you are interested, can go on with sharing on Bigtable / HDFS / HBASE and other more state of the art solutions.
I used to encounter an interesting issue, the Redis call has an increase in latency after I upgrade the network library dependency of my service RPC framework. The reason was that the pollers of RPC networker library occupy too much CPU and it grabs the default Redis netpoller’s CPU schedule. However, I could barely understand what happened in the networking part of the framework. So this session I will do a rough introduction on network packages
This essay is a follow up introduction on IM Architecutre. We will discuss some common consistency, avilability and partition tolerance issues we face in a multi-datacenter, distributed architecture of the IM system. We will also discuss how we tackle with thess issues in the service implementation to acieve high avaliblity and parition tolerance meanwhile achieving final consistency.