<?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>Go on BvBeJ的小站</title><link>https://www.bvbej.com/tags/go/</link><description>Recent content in Go on BvBeJ的小站</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Tue, 26 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.bvbej.com/tags/go/feed.xml" rel="self" type="application/rss+xml"/><item><title>Go 事件驱动 Saga：跨服务事务编排</title><link>https://www.bvbej.com/posts/go-event-driven-saga/</link><pubDate>Tue, 26 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-event-driven-saga/</guid><description>Saga 成功落地的关键是补偿动作和状态追踪</description></item><item><title>Go 中用 Feature Flag 做渐进发布的工程边界</title><link>https://www.bvbej.com/posts/go-openfeature-progressive-delivery/</link><pubDate>Mon, 25 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-openfeature-progressive-delivery/</guid><description>开关体系不是 if-else 管理器，而是发布控制平面的关键组件。</description></item><item><title>Go HTTP 连接池调优：避免隐性端口耗尽</title><link>https://www.bvbej.com/posts/go-http-connection-pooling/</link><pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-http-connection-pooling/</guid><description>默认参数并不适合所有流量模型，连接复用要可观测</description></item><item><title>Go 多租户限流中的公平性设计</title><link>https://www.bvbej.com/posts/go-multi-tenant-rate-limit-fairness/</link><pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-multi-tenant-rate-limit-fairness/</guid><description>全局限流保护系统，但租户公平性决定了商业可用性。</description></item><item><title>Go + Redis Pipeline：吞吐提升与延迟权衡</title><link>https://www.bvbej.com/posts/go-redis-pipeline-latency/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-redis-pipeline-latency/</guid><description>批量请求能降 RTT，但要控制单批大小和超时</description></item><item><title>Go HTTP/3 网关可观测性：QUIC 指标该怎么看</title><link>https://www.bvbej.com/posts/go-http3-gateway-observability/</link><pubDate>Mon, 18 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-http3-gateway-observability/</guid><description>HTTP/3 引入连接迁移与流级控制后，传统 TCP 指标已不够。</description></item><item><title>Go API 版本管理：平滑演进而不破坏旧客户端</title><link>https://www.bvbej.com/posts/go-api-versioning-strategy/</link><pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-api-versioning-strategy/</guid><description>版本治理不是多一个路径前缀，而是兼容策略设计</description></item><item><title>分布式 ID 生成中的时钟漂移治理</title><link>https://www.bvbej.com/posts/go-id-generator-clock-drift/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-id-generator-clock-drift/</guid><description>Snowflake 类方案最怕时间回拨，治理重点在时钟与熔断策略。</description></item><item><title>Go 数据库事务重试：何时该重试，何时应失败</title><link>https://www.bvbej.com/posts/go-db-transaction-retry/</link><pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-db-transaction-retry/</guid><description>重试策略必须和幂等语义一起设计</description></item><item><title>Go GC 延迟预算化：把“偶发抖动”变成可管理指标</title><link>https://www.bvbej.com/posts/go-gc-latency-budgeting/</link><pubDate>Wed, 13 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-gc-latency-budgeting/</guid><description>GC 问题不是关掉 GC，而是让内存增长和延迟目标协同。</description></item><item><title>Go Context 传递清单：避免超时与取消失控</title><link>https://www.bvbej.com/posts/go-context-propagation-checklist/</link><pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-context-propagation-checklist/</guid><description>context 用错会把请求链路变成隐式定时炸弹</description></item><item><title>Go + Redis 热点 Key 治理：从识别到分片</title><link>https://www.bvbej.com/posts/go-redis-hotkey-sharding/</link><pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-redis-hotkey-sharding/</guid><description>热点 Key 不只影响延迟，还会放大主从复制与集群迁移风险。</description></item><item><title>Go 服务降级手册：高峰期先保核心链路</title><link>https://www.bvbej.com/posts/go-graceful-degradation-playbook/</link><pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-graceful-degradation-playbook/</guid><description>降级不是放弃功能，而是把有限资源优先给最关键请求</description></item><item><title>Go 配置热更新：动态生效与安全边界</title><link>https://www.bvbej.com/posts/go-config-hot-reload/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-config-hot-reload/</guid><description>热更新能提高运维效率，但要明确哪些配置可以在线改，哪些不行</description></item><item><title>Go gRPC Streaming 的流控与内存治理</title><link>https://www.bvbej.com/posts/go-grpc-stream-flow-control/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-grpc-stream-flow-control/</guid><description>流式接口的瓶颈常在接收端消费能力，而不是网络带宽。</description></item><item><title>Go Kafka Consumer：重平衡期间的可用性设计</title><link>https://www.bvbej.com/posts/go-kafka-consumer-rebalance/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-kafka-consumer-rebalance/</guid><description>消费者重平衡是常态，关键是如何减少抖动和重复消费</description></item><item><title>Go 实现 Raft 时的日志压缩与快照传输细节</title><link>https://www.bvbej.com/posts/go-raft-log-compaction/</link><pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-raft-log-compaction/</guid><description>日志增长不可怕，可怕的是快照节奏和复制窗口设计错误。</description></item><item><title>Go 服务发现容错：注册中心抖动时怎么保服务</title><link>https://www.bvbej.com/posts/go-service-discovery-fallback/</link><pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-service-discovery-fallback/</guid><description>服务发现不是只有查地址，真正上线要考虑缓存、退避和降级</description></item><item><title>Go 幂等设计：防重试、防重复提交、防重复消费</title><link>https://www.bvbej.com/posts/go-idempotency-design/</link><pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-idempotency-design/</guid><description>幂等不是支付系统专属，几乎所有关键写操作都需要</description></item><item><title>Go Worker Pool：饱和控制与降级策略</title><link>https://www.bvbej.com/posts/go-worker-pool-saturation-control/</link><pubDate>Mon, 27 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-worker-pool-saturation-control/</guid><description>Worker Pool 不是为了并发更高，而是为了并发可控</description></item><item><title>Go 服务零停机数据库 Schema 迁移实战</title><link>https://www.bvbej.com/posts/go-zero-downtime-schema-migration/</link><pubDate>Mon, 27 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-zero-downtime-schema-migration/</guid><description>把 DDL 变更拆成可回滚、可观测、可灰度的迁移链路，避免高峰期雪崩。</description></item><item><title>Go 缓存一致性：更新策略与失效控制</title><link>https://www.bvbej.com/posts/go-cache-consistency-patterns/</link><pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-cache-consistency-patterns/</guid><description>缓存不是加上 Redis 就结束，真正难的是更新路径和一致性语义</description></item><item><title>Go 服务优雅重启：systemd 配合实践</title><link>https://www.bvbej.com/posts/go-graceful-restart-systemd/</link><pubDate>Thu, 23 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-graceful-restart-systemd/</guid><description>不丢连接、不打断在途请求的发布方案</description></item><item><title>Go Worker Pool 与背压：不靠拍脑袋定并发数</title><link>https://www.bvbej.com/posts/go-workerpool-backpressure-tuning/</link><pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-workerpool-backpressure-tuning/</guid><description>通过吞吐、延迟、队列深度三个指标，系统化调优 worker pool</description></item><item><title>Go Context 取消链路：别让 goroutine 泄漏</title><link>https://www.bvbej.com/posts/go-context-cancellation-patterns/</link><pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-context-cancellation-patterns/</guid><description>围绕 context 的传播、超时与取消，建立可维护的并发边界</description></item><item><title>Go gRPC 服务治理：超时、重试、熔断怎么配合</title><link>https://www.bvbej.com/posts/go-grpc-resilience-patterns/</link><pubDate>Thu, 16 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-grpc-resilience-patterns/</guid><description>gRPC 用起来不难，难的是在真实线上环境里把失败场景处理得足够稳</description></item><item><title>Go 服务监控进阶：从指标采集到 SLI / SLO 告警</title><link>https://www.bvbej.com/posts/go-sli-slo-alerting/</link><pubDate>Thu, 16 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-sli-slo-alerting/</guid><description>可观测性不是把 Prometheus 接上就结束了，真正难的是定义对业务有意义的指标和告警</description></item><item><title>Docker 多阶段构建：让你的镜像小而美</title><link>https://www.bvbej.com/posts/docker-multi-stage-build/</link><pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/docker-multi-stage-build/</guid><description>用多阶段构建把 Go 镜像从 800MB 压到 8MB，还顺带优化构建速度</description></item><item><title>从零理解分布式追踪：OpenTelemetry 实战</title><link>https://www.bvbej.com/posts/opentelemetry-distributed-tracing/</link><pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/opentelemetry-distributed-tracing/</guid><description>用 OpenTelemetry 给微服务装上 X 光机，看清每一次调用链路</description></item><item><title>Go 服务限流：用令牌桶保护你的 API</title><link>https://www.bvbej.com/posts/go-rate-limiting-middleware/</link><pubDate>Tue, 14 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-rate-limiting-middleware/</guid><description>从单机中间件到分布式实践，聊聊 Go 服务里的限流设计</description></item><item><title>Go 微服务可观测性：日志、指标、追踪实战</title><link>https://www.bvbej.com/posts/go-microservices-observability/</link><pubDate>Sat, 11 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-microservices-observability/</guid><description>不做好可观测性，微服务出问题就是灾难</description></item><item><title>Go 并发模式：Pipeline 实战</title><link>https://www.bvbej.com/posts/go-concurrency-patterns/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-concurrency-patterns/</guid><description>聊聊 Go 中 Pipeline 的设计模式与最佳实践</description></item><item><title>Kubernetes Operator 开发实战：用 Go 告别手动运维</title><link>https://www.bvbej.com/posts/kubernetes-operator-development/</link><pubDate>Sat, 04 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/kubernetes-operator-development/</guid><description>从 CRD 到 Controller，带你写一个生产级的 K8s Operator</description></item></channel></rss>