Portfolio ↗

Quiz

2988 questions of the kind that actually get asked — in interviews, in architecture review boards, and by the person who has to run the thing at 3 AM. Every answer states the trade-off rather than the slogan, and says when the obvious choice is the wrong one.

All areas2988 Architecture Fundamentals91 Distributed Systems111 Data Architecture100 Cloud Architecture97 Networking96 API & Integration Architecture97 Reliability & Resilience99 Observability92 Performance & Capacity Engineering100 Security Architecture105 Cost Architecture & FinOps102 Business Architecture103 Architecture Communication102 Enterprise Architecture100 Legacy Modernization102 AI-Era Architecture106 Software Architecture & Engineering93 Architecture Patterns94 Architecture Decision-Making101 The Architect's Meta-Skills102 Delivery & Release Engineering103 Platform Engineering & Developer Experience102 Testing & Quality Architecture102 Data Platform Architecture98 Streaming & Real-Time Data103 Data Governance & Semantics91 Frontend & Experience Architecture101 Edge, Mobile & IoT98 Regulatory & Data Protection Architecture99 Assurance, Audit & Model Risk98
Difficulty Any beginner intermediate advanced

5 questions in API Versioning.

  1. API Versioning advanced

    A payments API has thousands of integrators on many SDK versions. How should versioning, deprecation, compatibility testing and migration tooling be designed?

    2 min answer razorpayversioningdeprecationcompatibility
  2. API Versioning advanced

    A public API must keep every historical version working for thousands of integrators while the team keeps shipping breaking changes. Compare date-pinned per-account versioning with URL versioning and feature flags.

    3 min answer stripeapi-versioningbackward-compatibilitytransformations
  3. API Versioning advanced

    An API version used by about 3,000 integrators must be retired. Usage is long-tailed - 40 integrators account for 80% of calls and the remainder are small, some with no active developer. Give the sequence and say where it can go wrong.

    3 min answer deprecationsunsetversioningpartner communication
  4. API Versioning advanced

    An enterprise platform supports many years of API versions simultaneously because customers integrate deeply and upgrade slowly. What does that policy cost, and what would you do differently?

    2 min answer versioningdeprecationbackward-compatibilityenterprise
  5. API Versioning advanced

    You are designing a public payments API. Consumers are numerous, unknown and unmotivated to migrate. How do you handle breaking changes?

    2 min answer stripeapi-designversioningcompatibility