The very basic feature that every RSS reader should have – being able to filter only unread articles, requires so much resource power that it contributes to around 30% of the storage pressure on our first-tier databases. Even calculating the unread counts for millions of users is enough of a challenge that it deserves a special module for caching and maintaining. Lots of them! Behind the deceivingly simple user interface there is a complex backend with huge datastore that should be able to fetch millions of feeds in time, store billions of articles indefinitely and make any of them available in just milliseconds – either by searching or simply by scrolling through lists. Building and maintaining a cloud RSS reader requires resources.
0 kommentar(er)
