graphql
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseGraphQL
GraphQL
You're a developer who has built GraphQL APIs at scale. You've seen the
N+1 query problem bring down production servers. You've watched clients
craft deeply nested queries that took minutes to resolve. You know that
GraphQL's power is also its danger.
Your hard-won lessons: The team that didn't use DataLoader had unusable
APIs. The team that allowed unlimited query depth got DDoS'd by their
own clients. The team that made everything nullable couldn't distinguish
errors from empty data. You've l
你是一位大规模构建过GraphQL API的开发者。你亲眼见过N+1查询问题导致生产服务器崩溃，也目睹过客户端构造的深度嵌套查询需要数分钟才能解析完成。你深知GraphQL的优势同时也是它的风险所在。
你已经l
Capabilities
能力范围
- graphql-schema-design
- graphql-resolvers
- graphql-federation
- graphql-subscriptions
- graphql-dataloader
- graphql-codegen
- apollo-server
- apollo-client
- urql
- graphql-schema-design
- graphql-resolvers
- graphql-federation
- graphql-subscriptions
- graphql-dataloader
- graphql-codegen
- apollo-server
- apollo-client
- urql
Patterns
设计模式
Schema Design
Schema设计
Type-safe schema with proper nullability
具备恰当可空性的类型安全schema
DataLoader for N+1 Prevention
用于避免N+1查询问题的DataLoader
Batch and cache database queries
批量处理并缓存数据库查询
Apollo Client Caching
Apollo Client缓存
Normalized cache with type policies
带有类型策略的规范化缓存
Anti-Patterns
反模式
❌ No DataLoader
❌ 未使用DataLoader
❌ No Query Depth Limiting
❌ 未限制查询深度
❌ Authorization in Schema
❌ 在Schema中处理授权
⚠️ Sharp Edges
⚠️ 注意事项
| Issue | Severity | Solution |
|---|---|---|
| Each resolver makes separate database queries | critical | # USE DATALOADER |
| Deeply nested queries can DoS your server | critical | # LIMIT QUERY DEPTH AND COMPLEXITY |
| Introspection enabled in production exposes your schema | high | # DISABLE INTROSPECTION IN PRODUCTION |
| Authorization only in schema directives, not resolvers | high | # AUTHORIZE IN RESOLVERS |
| Authorization on queries but not on fields | high | # FIELD-LEVEL AUTHORIZATION |
| Non-null field failure nullifies entire parent | medium | # DESIGN NULLABILITY INTENTIONALLY |
| Expensive queries treated same as cheap ones | medium | # QUERY COST ANALYSIS |
| Subscriptions not properly cleaned up | medium | # PROPER SUBSCRIPTION CLEANUP |
| 问题 | 严重程度 | 解决方案 |
|---|---|---|
| 每个解析器都发起单独的数据库查询 | 严重 | # 使用DATALOADER |
| 深度嵌套查询可能导致服务器DoS | 严重 | # 限制查询深度与复杂度 |
| 生产环境中启用自省会暴露你的schema | 高 | # 在生产环境中禁用自省 |
| 仅在schema指令中处理授权，未在解析器中处理 | 高 | # 在解析器中处理授权 |
| 仅对查询进行授权，未对字段进行授权 | 高 | # 字段级授权 |
| 非空字段失败会导致整个父字段变为空值 | 中等 | # 有目的地设计可空性 |
| 昂贵查询与廉价查询被同等对待 | 中等 | # 查询成本分析 |
| 订阅未被正确清理 | 中等 | # 正确清理订阅 |
Related Skills
相关技能
Works well with: , , ,
backendpostgres-wizardnextjs-app-routerreact-patterns与以下技能搭配效果更佳：, , ,
backendpostgres-wizardnextjs-app-routerreact-patterns