Browse Cards

Alerting notifies teams when metrics or logs indicate problems that require attention.

Authentication verifies that users are who they claim to be, typically through passwords, tokens, or multi-factor methods.

Authorization determines what actions an authenticated user is permitted to perform within a system.

The blast radius is the scope of impact when something goes wrong. Smaller blast radius means fewer users affected by a failure.

A canary deployment releases changes to a small subset of users first, allowing you to detect issues before full rollout.

Encryption transforms data into an unreadable format that can only be decoded with the correct key.

E2E tests simulate real user workflows through the entire system. They catch integration issues but are slower and more brittle.

Feature flags allow you to toggle functionality on or off without deploying new code. They enable gradual rollouts and quick rollbacks.

Input validation ensures all user-provided data meets expected formats and constraints before processing.

Integration tests verify that multiple components work together correctly. They catch issues that unit tests miss.

Logging records events and state changes in your application for debugging and auditing purposes.

Metrics are numerical measurements collected over time that help you understand system behavior and performance.

Observability is the ability to understand a system's internal state by examining its outputs: logs, metrics, and traces.

A rollback strategy defines how to quickly revert to a previous working state when a deployment causes issues.

The test pyramid suggests having many unit tests, fewer integration tests, and even fewer end-to-end tests for optimal coverage and speed.

Unit tests verify individual functions or components in isolation. They are fast, reliable, and form the foundation of test coverage.