Work Flow of Webpage System Design

There are three workflows that we have to manage:

9.1. Changing the status of the users

• To update record statuses, users first authenticate through our authentication services.
• The data change request is then routed to the write services.
• The request is then pushed to the write queue, which accesses the master database to make the necessary modifications.
• These updates are subsequently mirrored in the slave database for consistency.
• The photos are then pulled from the write queue and stored in the CDN for quick delivery to the users.

9.2. Accessing the status of 10 million users

• For accessing the vast user database of 10 million records, users authenticate via our authentication services.
• Their request to view user statuses goes through the read services, which fetch a batch of data from the cache for immediate display.
• As users reach the end of a batch, new requests are sent to the servers for the next batch, ensuring seamless data presentation.
• Meanwhile, subsequent data batches are stored in the cache for quick retrieval.
• The photos of all the users are stored in the CDN, which is then accessed according to the batch.

9.3. Searching for any specific user

• When searching for any record, the search request is directed to our Search Services.
• It uses elastic search for searching the queries.
• Initial search attempts occur in the cache, which stores frequently accessed data.
• If the data is found there, it’s promptly returned to the user.
• If data is not found in the cache, the database is queried, and the results are provided to the user, with updates made to the cache for future searches.

We’ve got this huge community—over 10 million strong—and you want to build a webpage where everyone’s details, like their names, photos, those cool badges they’ve earned, and their points, can all be seen. That’s a massive load of information to handle. Achieving this goal necessitates an efficient and scalable system architecture capable of handling immense data volumes without compromising on performance or user experience.