NitroStack中间件和拦截器实战构建强大的请求处理管道【免费下载链接】nitrostackThe full-stack TypeScript framework to build, test, and deploy production-ready MCP servers and AI-native apps.项目地址: https://gitcode.com/gh_mirrors/ni/nitrostack在构建现代AI原生应用时高效的请求处理管道是确保系统稳定性和可扩展性的关键。NitroStack作为企业级TypeScript框架提供了强大的中间件和拦截器系统让开发者能够轻松构建复杂的请求处理逻辑。本文将深入探讨如何利用NitroStack的中间件和拦截器功能创建强大的请求处理管道。 为什么需要中间件和拦截器在AI应用开发中每个工具调用都需要处理各种横切关注点比如日志记录追踪请求执行过程性能监控测量执行时间身份验证验证用户权限数据验证确保输入数据格式正确响应格式化统一API响应格式错误处理优雅地处理异常情况NitroStack的中间件和拦截器系统正是为了解决这些问题而设计的让开发者能够专注于业务逻辑而不必重复编写基础设施代码。️ 中间件实战洋葱模型的核心中间件基础概念中间件遵循洋葱模型设计每个中间件层包裹着下一层最终到达处理器核心。在NitroStack中中间件主要用于请求处理前后的逻辑执行。创建日志中间件让我们从创建一个简单的日志中间件开始。这个中间件会记录每个请求的开始和结束时间import { Middleware, MiddlewareInterface, ExecutionContext } from nitrostack/core; Middleware() export class LoggingMiddleware implements MiddlewareInterface { async use(context: ExecutionContext, next: () Promiseany): Promiseany { const startTime Date.now(); const toolName context.toolName || unknown; console.log( 请求开始: ${toolName}, { requestId: context.requestId, timestamp: new Date().toISOString() }); try { const result await next(); const duration Date.now() - startTime; console.log(✅ 请求完成: ${toolName}, { requestId: context.requestId, duration, success: true }); return result; } catch (error) { const duration Date.now() - startTime; console.error(❌ 请求失败: ${toolName}, { requestId: context.requestId, duration, error: error instanceof Error ? error.message : String(error) }); throw error; } } }中间件的执行顺序中间件的执行顺序至关重要。NitroStack按照声明顺序执行中间件形成处理管道请求 │ ▼ RequestIdMiddleware生成请求ID │ ▼ LoggingMiddleware记录日志 │ ▼ AuthenticationMiddleware身份验证 │ ▼ AuthorizationMiddleware权限检查 │ ▼ ValidationMiddleware数据验证 │ ▼ 处理器执行 │ ▼ ValidationMiddleware后处理 │ ▼ AuthorizationMiddleware后处理 │ ▼ LoggingMiddleware记录结果 │ ▼ 响应在工具中使用中间件将中间件应用到具体的工具方法非常简单import { ToolDecorator as Tool, UseMiddleware } from nitrostack/core; import { LoggingMiddleware } from ./middleware/logging.middleware.js; import { ValidationMiddleware } from ./middleware/validation.middleware.js; export class ProductTools { Tool({ name: get_product, description: 获取产品详细信息 }) UseMiddleware(LoggingMiddleware, ValidationMiddleware) async getProduct(input: { productId: string }, ctx: ExecutionContext) { // 业务逻辑 return this.productService.findById(input.productId); } } 拦截器实战响应转换的艺术拦截器与中间件的区别虽然中间件和拦截器都用于处理横切关注点但它们的侧重点不同中间件主要用于请求处理前后的逻辑执行拦截器专注于请求和响应的转换创建响应包装拦截器响应包装拦截器可以统一所有API的响应格式import { Interceptor, InterceptorInterface, ExecutionContext } from nitrostack/core; Interceptor() export class ResponseWrapperInterceptor implements InterceptorInterface { async intercept(context: ExecutionContext, next: () Promiseany): Promiseany { const startTime Date.now(); // 执行处理器 const result await next(); // 统一响应格式 return { success: true, data: result, metadata: { tool: context.toolName, requestId: context.metadata?.requestId || context.requestId, timestamp: new Date().toISOString(), duration: Date.now() - startTime } }; } }敏感数据脱敏拦截器在处理用户数据时保护敏感信息至关重要Interceptor() export class DataMaskingInterceptor implements InterceptorInterface { private static readonly SENSITIVE_FIELDS [ password, ssn, socialSecurityNumber, creditCard, cardNumber, cvv, apiKey, secretKey, accessToken ]; async intercept(context: ExecutionContext, next: () Promiseany): Promiseany { const result await next(); return this.maskSensitiveData(result); } private maskSensitiveData(data: unknown): unknown { // 实现数据脱敏逻辑 // ... } }缓存拦截器提升性能缓存拦截器可以显著提升重复请求的响应速度import { Injectable } from nitrostack/core; Injectable() Interceptor() export class CacheInterceptor implements InterceptorInterface { private cache new Mapstring, { data: unknown; expiresAt: number }(); async intercept(context: ExecutionContext, next: () Promiseany): Promiseany { const cacheKey this.generateCacheKey(context); // 检查缓存 const cached this.cache.get(cacheKey); if (cached cached.expiresAt Date.now()) { console.log( 缓存命中, { key: cacheKey }); return cached.data; } // 执行处理器 const result await next(); // 存入缓存5分钟TTL this.cache.set(cacheKey, { data: result, expiresAt: Date.now() 5 * 60 * 1000 }); return result; } } 实战案例构建完整的请求处理管道场景电商产品查询API让我们构建一个完整的电商产品查询API包含完整的请求处理管道import { ToolDecorator as Tool, UseMiddleware, UseInterceptors, ExecutionContext } from nitrostack/core; // 导入自定义中间件和拦截器 import { RequestIdMiddleware } from ./middleware/request-id.middleware.js; import { LoggingMiddleware } from ./middleware/logging.middleware.js; import { AuthMiddleware } from ./middleware/auth.middleware.js; import { RateLimitMiddleware } from ./middleware/rate-limit.middleware.js; import { ResponseWrapperInterceptor } from ./interceptors/response-wrapper.interceptor.js; import { DataMaskingInterceptor } from ./interceptors/data-masking.interceptor.js; import { CacheInterceptor } from ./interceptors/cache.interceptor.js; export class ECommerceTools { Tool({ name: get_product_details, description: 获取产品详细信息, inputSchema: z.object({ productId: z.string().min(1), includeReviews: z.boolean().optional().default(false) }) }) UseMiddleware( RequestIdMiddleware, // 1. 生成请求ID LoggingMiddleware, // 2. 记录日志 AuthMiddleware, // 3. 身份验证 RateLimitMiddleware // 4. 限流控制 ) UseInterceptors( CacheInterceptor, // 5. 缓存检查 ResponseWrapperInterceptor, // 6. 响应包装 DataMaskingInterceptor // 7. 数据脱敏 ) async getProductDetails( input: { productId: string; includeReviews?: boolean }, ctx: ExecutionContext ) { // 业务逻辑 const product await this.productService.getById(input.productId); if (input.includeReviews) { const reviews await this.reviewService.getByProductId(input.productId); return { ...product, reviews }; } return product; } }管道执行流程这个完整的请求处理管道会按照以下顺序执行RequestIdMiddleware生成唯一请求IDLoggingMiddleware记录请求开始日志AuthMiddleware验证用户身份RateLimitMiddleware检查请求频率限制CacheInterceptor检查是否有缓存结果业务处理器执行核心业务逻辑DataMaskingInterceptor脱敏敏感数据ResponseWrapperInterceptor统一响应格式LoggingMiddleware记录请求完成日志 性能优化技巧1. 中间件顺序优化正确的中间件顺序可以显著提升性能UseMiddleware( RequestIdMiddleware, // 轻量级最先执行 RateLimitMiddleware, // 尽早拒绝过多请求 AuthMiddleware, // 验证身份 LoggingMiddleware, // 记录验证后的请求 ValidationMiddleware // 验证输入数据 )2. 条件执行中间件某些中间件可能不需要对所有请求执行Middleware() export class ConditionalMiddleware implements MiddlewareInterface { private readonly skipTools [health_check, ping, status]; async use(context: ExecutionContext, next: () Promiseany): Promiseany { // 跳过某些工具的中间件处理 if (this.skipTools.includes(context.toolName || )) { return next(); } // 执行中间件逻辑 return this.processRequest(context, next); } }3. 依赖注入中间件利用NitroStack的依赖注入系统创建可测试的中间件import { Injectable } from nitrostack/core; Injectable() Middleware() export class AuditMiddleware implements MiddlewareInterface { constructor( private auditService: AuditService, private configService: ConfigService ) {} async use(context: ExecutionContext, next: () Promiseany): Promiseany { const shouldAudit this.configService.get(ENABLE_AUDIT_LOG, true); if (!shouldAudit) { return next(); } const startTime Date.now(); const auditEntry { toolName: context.toolName, userId: context.auth?.subject, requestId: context.metadata?.requestId, timestamp: new Date().toISOString() }; try { const result await next(); await this.auditService.log({ ...auditEntry, status: success, duration: Date.now() - startTime }); return result; } catch (error) { await this.auditService.log({ ...auditEntry, status: error, duration: Date.now() - startTime, error: error instanceof Error ? error.message : String(error) }); throw error; } } }️ 最佳实践指南1. 单一职责原则每个中间件和拦截器应该只负责一件事情// ✅ 正确单一职责 Middleware() export class LoggingMiddleware { /* 只负责日志记录 */ } Middleware() export class AuthMiddleware { /* 只负责身份验证 */ } // ❌ 错误多重职责 Middleware() export class EverythingMiddleware { async use(context, next) { // 日志记录 身份验证 数据验证 缓存 // 难以测试和维护 } }2. 正确处理错误中间件和拦截器应该正确处理错误// ✅ 正确记录错误并重新抛出 async use(context: ExecutionContext, next: () Promiseany): Promiseany { try { return await next(); } catch (error) { context.logger.error(中间件捕获错误, { error }); throw error; // 重新抛出供上层处理 } } // ❌ 错误静默忽略错误 async use(context: ExecutionContext, next: () Promiseany): Promiseany { try { return await next(); } catch (error) { return null; // 错误被静默忽略 } }3. 避免数据突变拦截器应该返回新对象而不是修改原始数据// ✅ 正确返回新对象 async intercept(context, next) { const result await next(); return { ...result, transformed: true }; } // ❌ 错误修改原始数据 async intercept(context, next) { const result await next(); result.transformed true; // 突变原始数据 return result; }4. 文档化副作用清晰记录中间件和拦截器的副作用/** * 性能监控中间件 * * 记录执行时间到 context.metadata.executionTimeMs * 如果执行时间超过1000ms则记录警告 * * modifies context.metadata.executionTimeMs * logs 慢请求警告 */ Middleware() export class TimingMiddleware implements MiddlewareInterface { // 实现代码 } 实际应用场景场景1API监控系统Middleware() export class MetricsMiddleware implements MiddlewareInterface { private requestCounts new Mapstring, number(); private errorCounts new Mapstring, number(); private totalDuration new Mapstring, number(); async use(context: ExecutionContext, next: () Promiseany): Promiseany { const toolName context.toolName || unknown; const startTime Date.now(); // 增加请求计数 this.requestCounts.set(toolName, (this.requestCounts.get(toolName) || 0) 1); try { const result await next(); // 记录执行时间 const duration Date.now() - startTime; this.totalDuration.set(toolName, (this.totalDuration.get(toolName) || 0) duration); return result; } catch (error) { // 增加错误计数 this.errorCounts.set(toolName, (this.errorCounts.get(toolName) || 0) 1); throw error; } } getMetrics(): Recordstring, unknown { const tools: Recordstring, unknown {}; for (const [tool, count] of this.requestCounts) { tools[tool] { requests: count, errors: this.errorCounts.get(tool) || 0, avgDuration: (this.totalDuration.get(tool) || 0) / count }; } return { tools }; } }场景2请求上下文增强Middleware() export class ContextEnrichmentMiddleware implements MiddlewareInterface { async use(context: ExecutionContext, next: () Promiseany): Promiseany { if (context.metadata) { // 添加环境信息 context.metadata.environment process.env.NODE_ENV || development; context.metadata.serverVersion process.env.APP_VERSION || 1.0.0; // 添加用户上下文 if (context.auth?.subject) { context.metadata.userId context.auth.subject; context.metadata.userRoles context.auth.roles || []; } } return next(); } } 深入学习资源要深入了解NitroStack中间件和拦截器的更多细节可以参考以下资源官方文档docs/sdk/typescript/07-middleware-guide.md拦截器指南docs/sdk/typescript/08-interceptors-guide.md核心源码typescript/packages/core/src/core/middleware/拦截器实现typescript/packages/core/src/core/interceptors/ 总结NitroStack的中间件和拦截器系统为构建强大的请求处理管道提供了完整的解决方案。通过合理使用这些功能你可以提高代码复用性将横切关注点抽象为可重用的组件增强系统可维护性每个组件职责单一易于测试和维护提升开发效率专注于业务逻辑减少重复代码保证系统稳定性统一的错误处理和日志记录优化性能通过缓存和条件执行提升响应速度无论是构建简单的API还是复杂的企业级应用NitroStack的中间件和拦截器都能帮助你创建健壮、可扩展的请求处理管道。开始使用这些功能让你的AI应用开发更加高效和可靠【免费下载链接】nitrostackThe full-stack TypeScript framework to build, test, and deploy production-ready MCP servers and AI-native apps.项目地址: https://gitcode.com/gh_mirrors/ni/nitrostack创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考