liveBook · Manning

Error rate

As explained in Fast by Default

An error rate is the proportion of operations or requests that fail or produce errors.

Error rate measures the percentage of requests or operations that fail. For backend services, it is a core reliability metric alongside response-time percentiles and throughput. section 3.2.2

Small increases can trigger cascading failures: timeouts accumulate, retries overload systems, and circuit breakers trip. Reliability targets therefore belong in user-centered performance goals rather than isolated optimization work. section 3.2.2 section 3.6

Use error rate to:

  • Track the percentage of requests that fail, such as payment requests returning errors. section 3.2.2
  • Evaluate reliability together with latency and throughput, using APM dashboards or comparable observability tools. section 3.2.2
  • Set specific targets before optimization, then validate them with field data and lab data. section 3.6
Table 3.4 Backend performance metrics
Metric
Measures
Example
Response time percentiles (e.g. p50, p95, p99)
How fast do requests complete across the distribution of requests
“p95 of 200ms” means 95% of requests complete within 200ms
Throughput
Requests handled per second
Service handles 500 requests per second at peak
Error rate
Percentage of requests that fail
0.05% of payment requests return errors

Compare error rate with response-time percentiles and throughput in a backend performance-metrics table. section 3.2.2

How Fast by Default covers it

How deep it goes
Defines the metric, gives a payment example, and explains cascading consequences without detailing error classification or remediation.
Examples
Uses payment requests returning errors and APM dashboards displaying error rate with latency and throughput.
What it assumes
Assumes familiarity with backend requests and performance measurement while defining error rate from the beginning.
What you can do after
Evaluate backend reliability, set measurable targets, and validate performance changes with lab and field data.
How it connects
Connects error rate with response-time percentiles, throughput, timeouts, retries, circuit breakers, and performance goals.

Also explained in

Compare how 10 books explain error rate →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Fast by Default. The section links point to the parts of the book it draws on.