# routing-system Published articles for routing-system. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How Smart Model Routing Can Cut LLM Costs by 10X DevFeed: [How Smart Model Routing Can Cut LLM Costs by 10X]() Original publisher: [Read original article]() Author: ByteByteGo Published: 2026-09-09T15:30:26Z Content type: article Language: en Sources: [ByteByteGo]() Topics: [Model Routing](), [Large Language Model](), [API]() Tags: [cost](), [llm](), [model-routing](), [models](), [routing](), [routing-system](), [tokens]() ### AI overview This article explains how smart model routing can reduce LLM application costs by sending simple requests to less expensive models and difficult requests to more capable models. It notes that savings and response quality depend on request types, model price differences, and routing performance, and discusses router, cascading, semantic, and learned routing approaches. ### Source excerpt Cost reduction isn't a given. It also depends on the types of requests the application receives, the price difference between models, and how well the routing system performs. In this article, we are going to look at various aspects ## Make scalable routing system for your Flutter Apps DevFeed: [Make scalable routing system for your Flutter Apps]() Original publisher: [Read original article]() Author: Kanan Yusubov Published: 2026-07-29T15:25:43Z Content type: tutorial Language: en Sources: [Flutter Community - Medium]() Topics: [Flutter](), [Routing (disambiguation)](), [navigation](), [modules](), [Dependency injection](), [Usability]() Tags: [clean-architecture](), [dependency-injection](), [flutter](), [go-router](), [modular-router](), [modules](), [navigation](), [router](), [routing](), [routing-system](), [usability]() ### AI overview This tutorial describes a scalable, decoupled routing system for Flutter apps. It explains a wrapper built on go_router that adds typed route arguments, native and path parameters, cross-module modularization, nested routes, presentation modes, and type-safe route guards. ### Source excerpt Recently, I've been working on migrating our app's routing system. We previously used auto_route, but eventually realized its tightly coupled nature made it incredibly difficult to scale across independent modules. Furthermore, its heavy reliance on code generation became a bottleneck for our workflow. To resolve this, we decided to architect a clean, scalable, and highly decoupled routing system. Our new solution is a powerful wrapper built on top of go_router. It abstracts away the raw string navigation and supercharges the router with custom features to maximize usability and type safety. In this blog post, I will walk you through the core benefits of this new routing system, covering the following key topics: Unified Routing Protocol (AppRouteInfo) Strictly Typed Route Arguments Native & Path Parameters Support Cross-Module Modularization (AppModuleRouter) Hierarchical Back stack & Sub-Routes (Nested Route Definitions, Decoupled Cross-Module Navigation) Dynamic Presentation Modes (e.g., Native, ModalSheet, NoTransition) Guard Interceptor Mechanism (Type-Safe Redirects, Global Interceptors) Note: This blog will show the general usage and problems it solved. For more detailed code, you can check the following link: https://github.com/thisisyusub/scalable-routing-system-demoArchitectural Structure of Routing System Here is how the demo application is structured to achieve a fully decoupled, scalable routing system: scalable_routing_system_demo (main app): The entry point of the application responsible for wiring up all services, dependency injection, and global route configurations. app_routes: Houses all route definitions, parameters, routing protocols, and models to ensure fully type-safe navigation. This is decoupled from the core routing package to separate app-specific business needs from generic routing mechanics. routing_system (core router): A generic, domain-agnostic router package that has zero knowledge of the app's specific routes. It exclusively provid ## The "simple" 38 step journey to getting an RFC DevFeed: [The "simple" 38 step journey to getting an RFC]() Original publisher: [Read original article]() Author: ben@benjojo.co.uk Published: 2024-12-05T10:43:41Z Content type: opinion Language: en Sources: [benjojo blog]() Topics: [Internet Engineering Task Force (IETF)](), [protocols](), [networking](), [routing-system](), [Internet]() Tags: [ietf](), [network](), [protocols](), [rfc](), [routing](), [routing-system](), [tcp](), [tcp-ip](), [udp]() ### AI overview A firsthand account of the three-and-a-half-year process of developing RFC9687 and navigating the Internet Engineering Task Force process. It explains when pursuing IETF standardization is appropriate, including cases involving changes to established protocols that affect the broader Internet routing system. ### Source excerpt The "simple" 38 step journey to getting an RFC The Internet is built on the mutual understanding of network protocols and practices, and most of those protocols are defined using Request For Comments (RFC) or Best Common Practices (BCP) documents.