<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>并发 on Plbear | 后端架构 · AI工程 · 云原生技术博客</title><link>https://www.plbear.com/tags/%E5%B9%B6%E5%8F%91/</link><description>Recent content in 并发 on Plbear | 后端架构 · AI工程 · 云原生技术博客</description><generator>Hugo</generator><language>zh-cn</language><lastBuildDate>Wed, 06 Aug 2025 09:00:00 +0800</lastBuildDate><atom:link href="https://www.plbear.com/tags/%E5%B9%B6%E5%8F%91/index.xml" rel="self" type="application/rss+xml"/><item><title>Go 内存模型：happens-before 与并发安全</title><link>https://www.plbear.com/posts/2025-08-06-go-memory-model/</link><pubDate>Wed, 06 Aug 2025 09:00:00 +0800</pubDate><guid>https://www.plbear.com/posts/2025-08-06-go-memory-model/</guid><description>为什么不加锁的并发读可能读到旧值？Go 内存模型的 happens-before 规则、可见性、数据竞争——并发编程的地基，比 goroutine 语法重要得多。</description></item><item><title>Go 并发模式：goroutine + channel 实战</title><link>https://www.plbear.com/posts/2022-11-16-go-concurrency-patterns/</link><pubDate>Wed, 16 Nov 2022 09:00:00 +0800</pubDate><guid>https://www.plbear.com/posts/2022-11-16-go-concurrency-patterns/</guid><description>不要用锁解决问题，用通信。Worker Pool、Fan-out/Fan-in、超时控制、优雅退出——Go 并发编程的四个高频模式，每个都附可直接用的代码。</description></item></channel></rss>