Whenever you're ready, walk me through how you'd approach this.
LLD: Splitwise - entities, APIs, DB schema, classes
Asked in the Round 3 - Design stage. Reported follow-ups: Simplify debt algorithm (graph approach / two heaps).
Design the low-level architecture for a Splitwise-like expense-sharing system. Define the core entities and class relationships, REST APIs, database schema, and service boundaries. Explain how expenses, participants, shares, settlements, and balances are represented. Then design an algorithm to simplify outstanding debts, first using a graph approach and then discussing a two-heaps implementation. Address validation, idempotency, transaction consistency, and complexity.