Medium
Atlassian

Design a Work-Item Time Metrics Microservice System Design Interview

Design a microservice within a project-management platform that computes time-in-state and SLA metrics from work-item state history.

1. Problem Statement

Design a microservice that consumes work-item state-transition events from a project-management platform and exposes APIs to query how long items have spent in each workflow state, along with SLA compliance metrics. Where would you start?

2. Architecture Discussion Map

Use this as one discussion aid, not a single correct answer. Your design should follow from the requirements, scale, and trade-offs you establish.

Rendering architecture diagram...
Mermaid Source (For AI Bots)
graph LR
    A["Design a Work-Item Time Metrics Microservice"]
    A --> F1["Event ingestion from work-item state transitions"]
    A --> F2["Time-in-state calculation per issue, per project, aggregate"]
    A --> F3["SLA breach detection and alerting"]
    A --> F4["API design for metric queries"]
    A --> F5["Storage model for state history vs aggregated metrics"]
    A --> F6["Eventual consistency and late-arriving events"]

3. Key Focus Areas

  • 1
    Event ingestion from work-item state transitions
  • 2
    Time-in-state calculation (per issue, per project, aggregate)
  • 3
    SLA breach detection and alerting
  • 4
    API design for metric queries
  • 5
    Storage model for state history vs aggregated metrics
  • 6
    Eventual consistency and late-arriving events

Want interactive feedback?

Practice drawing this system component-by-component on a live whiteboard while the interviewer probes at your target level.

Start Interview

Core Concepts

System DesignMicroservicesEvent StreamingTime-Series Metrics