Path-Based Versioning (Most Common for Learning)
Header-Based Versioning (More Advanced)
Query Parameter Versioning (Not Recommended Long-Term)
Why Architects Insist on Route Versioning
From an architecture standpoint:
Multiple teams deploy independently
Some clients lag behind
Systems must be stable, not just correct
Route versioning:
Reduces outages
Enables parallel development
Prevents “surprise” failures
Provider Route Versioning Style Example
Google APIs Path-based major version /v1/projects
AWS service APIs Date-based / parameter-based Version=2016-11-15
AWS API Gateway (your APIs) Path-based major version /v1/orders