Design a Faster App Store | System Design

We've all experienced times when the App Store search is slow. This video dives into a high level overview of a (consistently) performant and scalable system to enable users to search, browse, and download apps.

Table of Contents:
0:00 - Introduction
0:45 - Requirements
1:38 - App Database
3:00 - API
4:05 - CDN
4:40 - App Search
5:58 - App Search: Caching
6:46 - Download Metrics
8:00 - Conclusion

Socials:

[pieter]

Another great video. Happy to report this is exactly the architecture I would have drawn up, so that's progress from some months ago. (Except maybe for the time series db.)

[fireballb]

imho, the downside of the timeseries db is that you will repeat calculations every time you want to know the total downloads or the top ones. In that case, I would have stored the data in the database on a field that counts the total downloads and then search from there. The issue in this case is that you will probably have deadlocks or concurrency problems because of the reads and writes, mostly on the top used apps. in this case, the db should be sharded so reads occur in one db shard and writes on the other ones. then automatically the db will update the data from one shard with the other ones. Aside from that, great design and i think the combination of db and elastic is a great choice

[drhdev]

Hey guys, what is the purpose of signing up if you are putting all the videos out for free?