Link to Video

Functional Requirements :

• Store Profiles

  • How many images will be stored per user ?

• Recommend Matches

  • How many active users ?

• Note the matches

  • How many matches you need to store ? (0.1% matches)

• Direct Messaging

  

                                                 Tinder Architecture
  

→ How to store images ?

Should we store images as file or Blob (Binary Large Object).

Some features that databases provide :

• Mutability (Not needed for images)
• Transaction (Not needed for images)
• Indexes (Not needed for images)
• Access Control (Needed for images) but can get from file system as well.

Static images so build a CDN (Content Discovery Network), fast retrieval. The file url will be stored in distributed file systems.

→ Architecture

Registration

User sends request to profile service for registration. But if you have other services, when user sends request to them, user needs to be authenticated again. This means that a lot of duplicated code for oauth. A way to avoid this is by using gateways.

Noone talks to client except the gateways. It just takes the request from client and asks profile service if it should serve the request. If yes , then it redirects the request to the correct service. This is decoupling the systems.

Images

Have a separate image service for storing images. This service will have a distributed file system, a database for storing image url and ID. Direct Messaging