System Design of Splitwise

System Design of Backend for Expense Sharing Apps like Splitwise

In this post, we will look into the System Design of Expense Sharing Applications such as Splitiwse. We will deep dive into the LLD of Splitwise, the Happy Flow of Splitwise, and also how to design the backend for Splitwise or such Expense Sharing Applications.

Table of Content

  • About Expense-Sharing Applications
  • System Design of Splitwise
  • Step 1: Defining Happy Flow for Splitwise
  • Step 2: Requirement Analysis/Gathering Requirements of Splitwise
  • Step 3: Low-Level Design (LLD) of Splitwise
  • Scaling Splitwise- How It Is Achievable Invoking Caching

Similar Reads

About Expense-Sharing Applications

...

System Design of Splitwise

Expense-sharing applications are used to log, track, and monitor the expenses of users with each other or in a group. The most famous example of such an application is Splitwise....

Step 1: Defining Happy Flow for Splitwise

Step 1: Defining Happy Flow for Splitwise...

Step 2: Requirement Analysis/Gathering Requirements of Splitwise

Let us first define a happy flow corresponding to which we will easily be able to plot out requirement gathering:...

Step 3: Low-Level Design (LLD) of Splitwise

Prioritized Requirements:...

Scaling Splitwise- How It Is Achievable Invoking Caching

3.1: Defining Objects | Splitwise LLD...