6. What is Routing in Backend? How Requests Find Their Way Home

Routing in HTTP: Understanding Methods and Paths

Introduction to Routing

• Routing expresses the "where" of a request, indicating which resource the server should interact with based on the intent defined by HTTP methods.

• Each HTTP method (GET, POST, etc.) describes an action or intent regarding data manipulation—fetching, adding, updating, or deleting resources.

Mapping Requests to Handlers

• The combination of HTTP method and route path maps to specific server-side logic that processes requests and returns appropriate responses.

• For example, a GET request to /api/sl/books retrieves an array of books from the server. The URL path indicates the resource being accessed.

Static vs Dynamic Routes

Static Routes

• Static routes do not contain variable parameters; they remain constant for every request (e.g., /api/sl/books). This consistency allows predictable responses.

Dynamic Routes

• Dynamic routes include variable parameters within their paths (e.g., /api/sl/users/:id), allowing for more flexible interactions such as fetching details for a specific user identified by their ID.

• The server extracts these dynamic parameters from the route to perform operations like database queries based on user IDs provided in requests.

Parameters in API Requests

Path Parameters

• Path parameters are dynamic segments of a URL that provide context about the resource being requested (e.g., :id in /api/sl/users/:id). They enhance semantic clarity in REST APIs by making URLs human-readable.

Query Parameters

• Query parameters follow a question mark in URLs and consist of key-value pairs used primarily with GET requests when no body is present (e.g., /api/sl/search?query=value). They allow additional metadata to be sent alongside requests without altering the main route structure.

Pagination and Filtering with Query Parameters

• Query parameters can also facilitate pagination and filtering results returned by APIs, enabling clients to specify limits on data retrieval (e.g., page numbers). This enhances usability when dealing with large datasets.

Nested Routes for Semantic Clarity

• Nested routes express relationships between resources clearly through hierarchical structures (e.g., /api/users/:userId/posts/:postId), allowing clients to fetch related data efficiently while maintaining semantic meaning throughout API calls.

Versioning and Deprecation in APIs

Route Versioning Explained

• Route versioning involves appending version identifiers (like v1 or v2) to API endpoints, facilitating changes over time without disrupting existing client applications using older versions of an API endpoint format.

Benefits of Versioning

• It provides clear communication about changes made between versions while allowing developers time to transition from deprecated versions smoothly before complete removal occurs from service offerings.

Catch-All Routes: Handling Unmatched Requests

Implementing Catch-All Logic

• A catch-all route captures any unmatched requests at the end of routing logic execution, providing users with friendly error messages instead of default null responses when attempting access outside defined endpoints.