MFA

An authentication method that requires more than one factor, such as password plus device or biometric proof.

Why it matters

MFA is useful because it gives engineers a shared vocabulary for designing, building, reviewing, and operating real systems. It helps teams reason about tradeoffs, failure modes, performance, and maintainability instead of treating implementation details as isolated facts.

Where it fits

This concept belongs in the product track, inside the web-applications layer. It often appears alongside authentication.

Mental model

Think of MFA as a named pattern or capability. When you can recognize it, you can ask better questions: what problem does it solve, what assumptions does it make, what can fail, and what neighboring concepts should be considered?

Subconcepts

• 2FA: MFA using two authentication factors.

  Common mistakes

  • Treating the term as a buzzword instead of connecting it to concrete engineering decisions.
  • Ignoring related constraints such as scale, security, ownership, observability, and failure recovery.

  Related concepts

  Study this together with authentication to understand how it behaves in a larger system.