惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

T
Tailwind CSS Blog
Hacker News - Newest:
Hacker News - Newest: "LLM"
The Cloudflare Blog
J
Java Code Geeks
大猫的无限游戏
大猫的无限游戏
雷峰网
雷峰网
WordPress大学
WordPress大学
Jina AI
Jina AI
IT之家
IT之家
Hugging Face - Blog
Hugging Face - Blog
博客园 - 聂微东
有赞技术团队
有赞技术团队
V
Vulnerabilities – Threatpost
博客园 - 司徒正美
L
Lohrmann on Cybersecurity
P
Privacy International News Feed
S
SegmentFault 最新的问题
C
Cisco Blogs
V
V2EX
博客园 - 三生石上(FineUI控件)
Apple Machine Learning Research
Apple Machine Learning Research
I
Intezer
人人都是产品经理
人人都是产品经理
博客园_首页
D
Darknet – Hacking Tools, Hacker News & Cyber Security
Cyberwarzone
Cyberwarzone
Know Your Adversary
Know Your Adversary
酷 壳 – CoolShell
酷 壳 – CoolShell
Security Latest
Security Latest
V
Visual Studio Blog
S
Schneier on Security
宝玉的分享
宝玉的分享
博客园 - 【当耐特】
腾讯CDC
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
博客园 - Franky
Last Week in AI
Last Week in AI
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
K
Kaspersky official blog
T
The Exploit Database - CXSecurity.com
G
GRAHAM CLULEY
量子位
S
Securelist
小众软件
小众软件
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
T
Tenable Blog
阮一峰的网络日志
阮一峰的网络日志
博客园 - 叶小钗
T
Troy Hunt's Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
Backend Routing Architecture — HTTP Methods, Path vs Query Params (2026)
Kaushikcoder · 2026-05-02 · via DEV Community

Demystifying API Routing: The Core of Modern Backend Architectures

Once a client request successfully navigates the internet and arrives at your server's doorstep, the critical next step is to understand what the client actually wants. This is where API routing, the backend's sophisticated traffic controller, takes center stage. It's the mechanism that translates raw network data into actionable instructions for your application, ensuring every request finds its intended destination.

Decoding the Request: Beyond the URL

Many developers, especially early in their careers, might perceive a URL like /api/products as a magical instruction that inherently knows whether to retrieve a list of products or create a new one. The reality, however, is far more fundamental. An incoming HTTP request is nothing more than a stream of text bytes transmitted over a TCP connection.

Consider a typical request for creating a new product:

POST /api/products HTTP/1.1
Host: example.com
Content-Type: application/json

{"name": "Widget X", "price": 29.99}

Enter fullscreen mode Exit fullscreen mode

The router, acting as the server's central switchboard, is responsible for parsing this raw string. It meticulously extracts key pieces of information, primarily the HTTP Method (POST) and the Request Path (/api/products). By combining these two elements (e.g., "POST:/api/products"), the router constructs a unique identifier. This identifier then allows it to swiftly look up and execute the precise backend function designed to handle that specific operation. The URL path merely provides context; the router imbues it with operational meaning.

Optimizing Request Handling: Static vs. Dynamic Paths

Not all API endpoints are treated equally by a router. Backend frameworks employ different strategies to process routes, aiming to maximize efficiency and minimize computational overhead.

Static Routes: Instant Matches (O(1) Performance)

A static route represents an exact, unchanging string match, such as /api/health or /api/status. Because these paths are fixed, frameworks can store them in highly optimized data structures, like hash maps or dictionaries. When a request for a static path arrives, the router performs a direct lookup (e.g., routes_dict["GET:/api/health"]). This operation boasts O(1) time complexity, meaning its speed is constant and unaffected by the total number of routes your application supports. It's exceptionally fast, regardless of your API's scale.

Dynamic Routes: The Flexible Workhorses

Dynamic routes, in contrast, incorporate variable segments within their paths, for instance, /api/users/{user_id}. A simple dictionary lookup won't suffice here, as an incoming request like /api/users/123 won't directly match the generic {user_id} pattern. The router must employ more sophisticated algorithms to parse the path, extract the variable (e.g., "123"), and then correctly map it to the appropriate handler.

Advanced Routing Algorithms: From Linear Scans to Tree Structures

The method by which a router extracts variables from dynamic paths significantly impacts performance.

The Regex Linear Search (O(N) Performance)

Historically, and in some older frameworks, dynamic routes were often compiled into Regular Expressions. When a request came in, the router would iterate through a list of all defined dynamic route regex patterns, attempting to match the incoming URL against each one sequentially. This constitutes an O(N) operation, where N is the number of dynamic routes. If the matching route is near the end of a long list, the lookup time can be noticeably slower.

The Radix Tree: Modern Speed (O(K) Performance)

Modern, high-performance frameworks have largely moved beyond linear regex matching. They instead organize dynamic URLs into a specialized data structure known as a Radix Tree (or Prefix Tree). This tree-based approach allows the router to traverse the URL path segment by segment. For example, when processing /users/123/orders, the router first checks the /users segment, immediately pruning away all routes that don't begin with /users. It then moves to /123, and so on. The search time becomes O(K), where K is the length of the URL path itself, making it significantly faster and more scalable than linear searches. This is a key factor in the speed of contemporary web frameworks.

Crafting Flexible APIs: Path and Query Parameters

When designing APIs, it's crucial to understand how to inject external data into your backend functions. The URL offers two primary locations for this, each serving a distinct purpose. Misusing them can lead to poorly designed and confusing APIs.

Path Parameters: Identifying Specific Resources

Path parameters are integral components of the URL's hierarchical structure. Their primary role is to uniquely identify a specific resource or entity within your system.

  • Example: /users/42/orders/9
  • Framework Representation: @app.get("/users/{user_id}/orders/{order_id}")
  • Nature: They are inherently mandatory. Omitting a path parameter (e.g., /users//orders/9) typically results in a 404 Not Found error, as the specific resource cannot be identified.
  • Conceptual Use: Use path parameters to pinpoint who or what your operation targets.

Query Parameters: Modifying Resource Presentation

Query parameters are appended to the end of a URL, following a question mark ?, with individual parameters separated by ampersands &. They do not identify a resource but rather modify how a collection of resources is presented or filtered.

  • Example: /products?category=electronics&limit=20&sort=price_desc
  • Nature: They are fundamentally optional. A well-designed API should anticipate their absence and provide sensible default values (e.g., if limit is missing, default to 10 items). The router extracts these into a key-value map for your backend logic.
  • Conceptual Use: Employ query parameters for filtering, sorting, pagination, or searching collections of data.

The Language of APIs: Understanding HTTP Methods and Idempotency

A hallmark of robust API design, particularly for senior architects, is adherence to REST (Representational State Transfer) principles. This means avoiding action-oriented URLs (e.g., /create_user) and instead using the URL to represent the noun (e.g., /users) while the HTTP Method conveys the verb or intended action.

HTTP Method Primary Intent Idempotent?
GET Retrieve a resource or collection. Must not alter server state. Yes (Repeatable without side effects)
POST Create a new resource. No (Repeating typically creates duplicates)
PUT Replace an existing resource entirely (or create if it doesn't exist). Yes (Repeating overwrites with the same data)
PATCH Apply partial modifications to an existing resource. Usually No (Order of operations might matter)
DELETE Remove a specified resource. Yes (Deleting an already deleted resource has no further effect)

Architectural Concept: Idempotency

An operation is idempotent if performing it multiple times yields the exact same state change as performing it once. This concept is vital for building resilient client-side retry logic. For example, if a user's network connection is unstable and they accidentally send a PUT request to update their profile five times, the outcome is safe: their profile is simply overwritten five times with the same data. Conversely, if they send a POST request five times to create an account, you might inadvertently create five duplicate user accounts. Understanding idempotency is crucial for designing APIs that can gracefully handle network inconsistencies and client retries.

Practical Application: Building a Custom Router

To truly grasp these concepts, consider the exercise of constructing a basic HTTP router from scratch, without relying on established frameworks like FastAPI or Django. This involves implementing the core mechanics: parsing a raw TCP string to extract the HTTP method, path, and query string. A foundational implementation might separate static routes into a fast dictionary lookup and dynamic routes into a list of regular expressions.

A significant challenge and performance upgrade would be to refactor such a router to utilize a Radix Tree structure for dynamic routes. Instead of iterating through regex patterns, the routing logic would split the incoming URL by slashes and traverse a nested dictionary or tree, mimicking the efficiency of modern frameworks and achieving O(K) lookup times.

Key API Design Considerations

When designing API endpoints, several common distinctions and practices emerge:

  • 404 vs. 405 Status Codes: A 404 Not Found indicates that the requested URL path (the resource) does not exist in the router's registry. In contrast, a 405 Method Not Allowed signifies that the URL path does exist, but the HTTP method used (e.g., attempting to POST to an endpoint that only supports GET) is not permitted for that resource. A well-engineered router automatically differentiates and returns the appropriate status.
  • Trailing Slashes in URLs: Whether to include a trailing slash (/users/ vs. /users) is primarily a stylistic choice in modern APIs. However, some routing frameworks implement "strict routing," treating these as distinct endpoints. To prevent broken links and ensure consistency, many routers automatically issue an HTTP 307 Redirect to guide clients to the canonical (slashed or non-slashed) version.
  • GET Requests with JSON Bodies: While the HTTP specification doesn't strictly forbid sending a JSON body with a GET request, it's a practice generally avoided. Many intermediate proxies, caching layers (like CDNs), and web servers are configured to strip the body from GET requests, preventing it from ever reaching your application. For complex search queries or data retrieval that requires a payload, the "Search POST" pattern, using a POST request with a JSON body, is a more reliable and widely supported approach.

Mastering how raw network traffic is parsed and routed into memory is a foundational skill for any backend developer.