Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 42 additions & 0 deletions src/content/posts/ep69.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
---
type: podcast-episode
status: published
slug: /posts/ep69
guid: 69
title: "EP69 GraphQL:治好前后端联调内耗"
subtitle: "强类型 schema 统一前后端协作,也聊 n+1、缓存和什么项目不该上 GraphQL"
publicationDate: 2026-06-24 14:00:00
author: AnnatarHe
season: 3
episodeNumber: 69
episodeType: full
excerpt: "EP69 GraphQL:治好前后端联调内耗:强类型 schema 统一前后端协作,也聊 n+1、缓存和什么项目不该上 GraphQL"
url: https://www.xiaoyuzhoufm.com/episode/6a3bab23ffcf45052c119264
size: 0
duration: 0
explicit: false
xyzLink: https://www.xiaoyuzhoufm.com/episode/6a3bab23ffcf45052c119264
youtubeId: t-8Ry_4s3mo
biliUrl: //player.bilibili.com/player.html?isOutside=true&aid=116794991842817&bvid=BV13y7K6EE2b&cid=39324093278&p=1
categories:
- graphql
- api
- restful
- schema
- frontend
- backend
- fullstack
- ai
---

### 📕 Shownotes

前后端怎么交互?大多数人第一反应都是 REST + HTTP。但接口越写越多、前后端对同一个字段理解对不齐、类型全靠猜——这些坑你大概率都踩过。

这期我们聊 GraphQL:一门出道十多年、却始终没真正普及的技术,为什么在 AI 时代反而值得重新认识。我们从 REST 的痛点出发,讲清楚 GraphQL 的强类型 schema 如何统一前后端协作、如何让缓存更聪明,以及为什么强类型对 AI 写代码是一个巨大的红利。

当然,GraphQL 不是银弹。我们也会聊它真实的坑:n+1 问题、缓存思维的转变、HTTP 状态码、以及什么项目压根不该上 GraphQL。

如果你在做一个中大型项目,或者想让 AI 帮你写出更靠谱的代码,这期也许能给你一些新思路。欢迎在评论区聊聊你对 GraphQL 的看法,记得关注 AsyncTalk 异步聊技术。

BGM by Otologic
Loading