Search the practice set

term

Throughput

The rate of work a system completes per unit of time — and a quantity that trades against latency rather than tracking it.

Performance & Capacity term

Competing Consumers

Multiple identical consumers reading from one queue, so throughput scales with consumer count and work is distributed automatically.

Architecture Patterns term

Little's Law Applied to Pools

Using L = λW to size connection and thread pools from measured throughput and latency rather than from a default.

Connection Pooling term

Non-Functional Requirement

A requirement about how well the system must behave rather than what it must do — latency, availability, throughput, security, cost.

Architecture Fundamentals term

Scalability

The ability to handle growing load by adding resources, ideally with cost rising no faster than the load.

Distributed Systems term

Wide-Column Store

A store organised as partitions of sorted rows, designed for very high write throughput and predictable single-partition reads at large scale.

NoSQL Stores

topic

Throughput

Work completed per unit time, and why it trades against latency.

Performance & Capacity Engineering — no content yet topic

Competing Consumers

Scaling throughput with instances, at the cost of ordering.

Architecture Patterns — no content yet topic

DORA Metrics

Throughput and stability moving together rather than trading off.

Software Architecture & Engineering — no content yet topic

Quality Attributes

Availability, latency, throughput, security, cost — expressed as testable scenarios.

Architecture Fundamentals — no content yet topic

Serverless vs Containers

Spiky and event-driven versus sustained throughput.

Architecture Decision-Making — no content yet