##### Question Design a scalable tagging system that supports creating tags, associating multiple tags with items, querying by single or combined tags, handling high read/write traffic, and ensuring consistency with sharding, caching, and indexing strategies.

This question evaluates understanding of distributed systems, data modeling, indexing, sharding, caching, consistency models, and multi-tenant architecture for building high-throughput tagging and query services.

How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

What difficulty level is this interview question?

This is a hard difficulty System Design question, commonly asked during Technical Screen rounds at Atlassian.

What role is this question designed for?

This question is commonly asked for Software Engineer candidates at Atlassian during technical interviews.

Design a scalable tagging system | Atlassian Interview Question

System Design: Scalable Tagging Service

Context

You are designing a multi-tenant tagging service for a large-scale SaaS product. Items (e.g., documents, issues, pages) can have multiple tags. The system must support high read/write throughput and efficient queries by one or multiple tags.

Assume scale on the order of:

100M items, 10M distinct tags, average 5–20 tags per item
Peak 10k read QPS, 2k write QPS (tag add/remove)
Multi-tenant isolation is required

Requirements

Create and manage tags
Associate/dissociate multiple tags with an item
Query items:
- by a single tag
- by a combination of tags (AND/OR), with pagination and sort (e.g., recency)
High availability and low latency for reads; scalable writes
Consistency model: clearly define and implement (eventual vs read-your-writes)
Sharding, caching, and indexing strategies for scale
Operability: monitoring, reindexing, backfills

Deliverables

Data model and storage choices
Read and write paths (including APIs)
Indexing strategy for tag queries (single and combined)
Sharding/partitioning plan
Caching strategy and invalidation
Consistency trade-offs and mechanisms
Handling hot tags, skew, and growth

Context

Assume scale on the order of:

100M items, 10M distinct tags, average 5–20 tags per item

Peak 10k read QPS, 2k write QPS (tag add/remove)

Multi-tenant isolation is required

Requirements

Create and manage tags

Associate/dissociate multiple tags with an item

Query items:

by a single tag
by a combination of tags (AND/OR), with pagination and sort (e.g., recency)

High availability and low latency for reads; scalable writes

Consistency model: clearly define and implement (eventual vs read-your-writes)

Sharding, caching, and indexing strategies for scale

Operability: monitoring, reindexing, backfills

Design a scalable tagging system

Quick Overview

System Design: Scalable Tagging Service

Context

Requirements

Deliverables

Solution

Comments (0)

Design a scalable tagging system

Quick Overview

System Design: Scalable Tagging Service

Context

Requirements

Deliverables

Solution

Comments (0)