248 lines
7.5 KiB
JSON
248 lines
7.5 KiB
JSON
{
|
||
"version": "1.0.0",
|
||
"updated": "2026-09-04",
|
||
"topics": [
|
||
{
|
||
"slug": "qunar-ai-fullstack",
|
||
"name": "去哪儿 AI 面 — AI 全栈方向",
|
||
"description": "覆盖 JVM/GC、AI Agent 架构、工具链、幻觉治理等核心考察领域",
|
||
"subtopics": [
|
||
{
|
||
"slug": "gc-jvm",
|
||
"name": "GC / JVM / 三色标记",
|
||
"description": "JVM 堆内存模型、GC 算法、三色标记法、垃圾收集器",
|
||
"path": "topics/qunar-ai-fullstack/gc-jvm",
|
||
"stats": {
|
||
"total": 20,
|
||
"by_type": {
|
||
"fill_blank": 10,
|
||
"single_choice": 10
|
||
}
|
||
}
|
||
},
|
||
{
|
||
"slug": "ai-structured-output",
|
||
"name": "AI 结构化输出 / Agent 架构",
|
||
"description": "结构化输出方法、Agent 模式、受限解码",
|
||
"path": "topics/qunar-ai-fullstack/ai-structured-output",
|
||
"stats": {
|
||
"total": 20,
|
||
"by_type": {
|
||
"fill_blank": 10,
|
||
"single_choice": 10
|
||
}
|
||
}
|
||
},
|
||
{
|
||
"slug": "ai-memory",
|
||
"name": "Agent 记忆管理 / 冲突处理",
|
||
"description": "记忆分层架构、淘汰策略、冲突检测与消解",
|
||
"path": "topics/qunar-ai-fullstack/ai-memory",
|
||
"stats": {
|
||
"total": 20,
|
||
"by_type": {
|
||
"fill_blank": 10,
|
||
"single_choice": 10
|
||
}
|
||
}
|
||
},
|
||
{
|
||
"slug": "ai-hallucination",
|
||
"name": "AI 幻觉 / 目标评价 / 规范",
|
||
"description": "幻觉分类、Critic 架构、Context Engineering、评估体系",
|
||
"path": "topics/qunar-ai-fullstack/ai-hallucination",
|
||
"stats": {
|
||
"total": 20,
|
||
"by_type": {
|
||
"fill_blank": 10,
|
||
"single_choice": 10
|
||
}
|
||
}
|
||
},
|
||
{
|
||
"slug": "ai-tooling",
|
||
"name": "AI 工具 / Harness / 综合",
|
||
"description": "AI 工具选型、Harness 架构、可靠性保障、提效分析",
|
||
"path": "topics/qunar-ai-fullstack/ai-tooling",
|
||
"stats": {
|
||
"total": 20,
|
||
"by_type": {
|
||
"fill_blank": 10,
|
||
"single_choice": 10
|
||
}
|
||
}
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"slug": "networking",
|
||
"name": "计算机网络",
|
||
"description": "从 HTTP 协议到底层连接管理，覆盖面试和实战中的核心网络知识",
|
||
"subtopics": [
|
||
{
|
||
"slug": "http-handshake",
|
||
"name": "HTTP 握手",
|
||
"description": "TCP 三次握手、TLS 握手、HTTP/2 与 HTTP/3 的连接建立",
|
||
"path": "topics/networking/http-handshake",
|
||
"stats": {
|
||
"total": 20,
|
||
"by_type": {
|
||
"single_choice": 10,
|
||
"fill_blank": 10
|
||
}
|
||
}
|
||
},
|
||
{
|
||
"slug": "http-connection-cost",
|
||
"name": "HTTP 连接资源消耗",
|
||
"description": "单连接资源开销、百万并发的真实数字与应对策略",
|
||
"path": "topics/networking/http-connection-cost",
|
||
"stats": {
|
||
"total": 20,
|
||
"by_type": {
|
||
"single_choice": 10,
|
||
"fill_blank": 10
|
||
}
|
||
}
|
||
},
|
||
{
|
||
"slug": "connection-pooling",
|
||
"name": "连接池复用",
|
||
"description": "预建连接、借还机制、HTTP/1.1 与 HTTP/2 的复用差异",
|
||
"path": "topics/networking/connection-pooling",
|
||
"stats": {
|
||
"total": 20,
|
||
"by_type": {
|
||
"single_choice": 10,
|
||
"fill_blank": 10
|
||
}
|
||
}
|
||
},
|
||
{
|
||
"slug": "http-keepalive",
|
||
"name": "HTTP Keep-Alive",
|
||
"description": "Keep-Alive 原理、队头阻塞、演进路线",
|
||
"path": "topics/networking/http-keepalive",
|
||
"stats": {
|
||
"total": 20,
|
||
"by_type": {
|
||
"single_choice": 10,
|
||
"fill_blank": 10
|
||
}
|
||
}
|
||
},
|
||
{
|
||
"slug": "keepalive-scenarios",
|
||
"name": "Keep-Alive 使用场景",
|
||
"description": "何时启用、何时关闭、生产环境最佳实践",
|
||
"path": "topics/networking/keepalive-scenarios",
|
||
"stats": {
|
||
"total": 20,
|
||
"by_type": {
|
||
"single_choice": 10,
|
||
"fill_blank": 10
|
||
}
|
||
}
|
||
},
|
||
{
|
||
"slug": "domain-sharding",
|
||
"name": "域名分片",
|
||
"description": "HTTP/1.1 时代的 hack，HTTP/2 后的淘汰",
|
||
"path": "topics/networking/domain-sharding",
|
||
"stats": {
|
||
"total": 20,
|
||
"by_type": {
|
||
"single_choice": 10,
|
||
"fill_blank": 10
|
||
}
|
||
}
|
||
},
|
||
{
|
||
"slug": "cdn",
|
||
"name": "CDN",
|
||
"description": "边缘节点、缓存策略、加速原理与配置",
|
||
"path": "topics/networking/cdn",
|
||
"stats": {
|
||
"total": 20,
|
||
"by_type": {
|
||
"single_choice": 10,
|
||
"fill_blank": 10
|
||
}
|
||
}
|
||
},
|
||
{
|
||
"slug": "cors",
|
||
"name": "跨域 CORS",
|
||
"description": "同源三元组、CORS 响应头、预检请求",
|
||
"path": "topics/networking/cors",
|
||
"stats": {
|
||
"total": 20,
|
||
"by_type": {
|
||
"single_choice": 10,
|
||
"fill_blank": 10
|
||
}
|
||
}
|
||
},
|
||
{
|
||
"slug": "go-build-strip",
|
||
"name": "Go 编译标志 -s",
|
||
"description": "剥离调试信息、体积优化、生产发布",
|
||
"path": "topics/networking/go-build-strip",
|
||
"stats": {
|
||
"total": 20,
|
||
"by_type": {
|
||
"single_choice": 10,
|
||
"fill_blank": 10
|
||
}
|
||
}
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"slug": "gc-special",
|
||
"name": "垃圾回收专题",
|
||
"description": "垃圾回收（GC）专题：GC 概念与代价、内存碎片与算法、分代 GC、回收器对比、GC Roots、三色标记法",
|
||
"subtopics": [
|
||
{
|
||
"slug": "gc-deep-dive",
|
||
"name": "GC 综合深入",
|
||
"description": "垃圾回收专题：GC 概念、内存碎片与算法、分代 GC、回收器对比、GC Roots、三色标记法",
|
||
"path": "topics/gc-special/gc-deep-dive",
|
||
"stats": {
|
||
"total": 50,
|
||
"by_type": {
|
||
"single_choice": 10,
|
||
"fill_blank": 10,
|
||
"true_false": 10,
|
||
"multiple_choice": 10,
|
||
"short_answer": 10
|
||
}
|
||
}
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"slug": "architecture",
|
||
"name": "系统架构",
|
||
"description": "高并发系统架构设计：秒杀系统、限流、削峰、数据一致性等",
|
||
"subtopics": [
|
||
{
|
||
"slug": "seckill-design",
|
||
"name": "高并发秒杀系统设计",
|
||
"description": "分层削峰、限流(429)、Redis Lua 原子扣减、不超卖、一人限购、异步落库、Redis Key 设计",
|
||
"path": "topics/architecture/seckill-design",
|
||
"stats": {
|
||
"total": 40,
|
||
"by_type": {
|
||
"single_choice": 10,
|
||
"fill_blank": 10,
|
||
"short_answer": 10,
|
||
"code_reading": 10
|
||
}
|
||
}
|
||
}
|
||
]
|
||
}
|
||
]
|
||
}
|