I guess this is applicable to any social media platform or other similar systems. Is it because there are always bugs to address, so it’s never really running smoothly, or other reasons?
In: 153
A site like Twitter is not fully self contained. It uses many (probably thousands) of third party libraries. These libraries are constantly being updated for new features, security risks, stability etc.
That means you need to frequently update your app to at the very least use the new libraries. Not doing so won’t break it right away, but sooner or later (hint: usually sooner) there will be a breaking change such as an older version being deprecated, or a field name being changed, that requires you to not only update the library you tell your program to use, but to make some changes internally as well.
Plus anything running at the scale of Twitter has a whole lot of infrastructure supporting it, usually in the cloud, that requires specific types of engineers (DevOps, DevSecOps, etc).
Latest Answers