Atlassian System Design Interview: Designing a Scalable Tagging System

I put together my end-to-end notes for designing a Tagging System, something that comes up frequently in system design interviews at companies like Atlassian. This covers: - Functional & non-functiona

I put together my end-to-end notes for designing a Tagging System, something that comes up frequently in system design interviews at companies like Atlassian. This covers: - Functional & non-functional requirements - Core entities (tags, entities, associations, tenants) - API design for tagging / untagging / querying - Database schema (read vs write patterns) - Scaling considerations - Analytics use cases (top tags, counts, pagination) I tried to focus not just on what to build, but why certain design choices are made (Postgres vs Cassandra, read/write separation, caching, etc.). Sharing this in case it helps others preparing for system design interviews. Feedback and improvements are welcome 🙂 Find the high res image here - https://files.catbox.moe/i48qph.png