<?xml version="1.0" encoding="utf-8" ?><rss version="2.0"><channel><title><![CDATA[hrfhrf32101的博客]]></title><description><![CDATA[]]></description><link>https://blog.youkuaiyun.com/hrfhrf32101</link><language>zh-cn</language><generator>https://blog.youkuaiyun.com/</generator><copyright><![CDATA[Copyright &copy; hrfhrf32101]]></copyright><item><title><![CDATA[DeepSeek-R1原理和使用]]></title><link>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145423404</link><guid>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145423404</guid><author>hrfhrf32101</author><pubDate>Sun, 02 Feb 2025 22:33:20 +0800</pubDate><description><![CDATA[DeepSeek-R1 通过结合强化学习和监督学习的方法，实现了在数学和逻辑推理等领域的高性能。在实际应用中，可以通过 API 调用或本地部署的方式使用 DeepSeek-R1 模型，解决多种复杂问题。]]></description><category></category></item><item><title><![CDATA[TIDB对比MYSQL]]></title><link>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145423199</link><guid>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145423199</guid><author>hrfhrf32101</author><pubDate>Sun, 02 Feb 2025 22:15:10 +0800</pubDate><description><![CDATA[TiDB 和 MySQL 在应对大数据存储与高效查询方面采用了完全不同的架构设计。三个维度进行对比分析，并结合真实生产场景给出选择建议。：某社交平台消息表（日均 20 亿条）：分表后 Join 查询超时。]]></description><category></category></item><item><title><![CDATA[TiDB 7.5.0 的核心实现]]></title><link>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145423134</link><guid>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145423134</guid><author>hrfhrf32101</author><pubDate>Sun, 02 Feb 2025 22:05:03 +0800</pubDate><description><![CDATA[Titan：Percolator事务协议 + 乐观锁：调度器Operator机制：Cascades优化器：列存同步 + MPP计算。]]></description><category></category></item><item><title><![CDATA[RocketMQ 5.1.3拆解]]></title><link>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145422942</link><guid>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145422942</guid><author>hrfhrf32101</author><pubDate>Sun, 02 Feb 2025 21:41:59 +0800</pubDate><description><![CDATA[把RocketMQ想象成高速公路系统，消息就是车辆，Broker是服务区。：CommitLog顺序写 + ConsumeQueue索引跳表：Netty主从Reactor线程模型：队列选择算法 + 内存屏障：DLedger多副本同步：长轮询Pull + 位点提交。]]></description><category></category></item><item><title><![CDATA[kafka3.6.0源码分析：问题分析和解决方案]]></title><link>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145422693</link><guid>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145422693</guid><author>hrfhrf32101</author><pubDate>Sun, 02 Feb 2025 21:30:13 +0800</pubDate><description><![CDATA[源码路径：clients/src/main/java/org/apache/kafka/clients/producer。源码路径：clients/src/main/java/org/apache/kafka/clients/consumer。源码路径：core/src/main/scala/kafka/network。源码路径：core/src/main/scala/kafka/cluster。源码路径：core/src/main/scala/kafka/log。【生产环境诊断公式】]]></description><category></category></item><item><title><![CDATA[Redis源码：深入分析redis设计漏洞]]></title><link>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145414434</link><guid>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145414434</guid><author>hrfhrf32101</author><pubDate>Sat, 01 Feb 2025 20:09:11 +0800</pubDate><description><![CDATA[Redis的设计哲学优点：用简单暴力换取大部分场景的高性能代价：对极端场景缺乏防御（如大key、高并发危险命令）血泪教训永远不要假设Redis是"纯内存操作就很快"时，可能触发同步的key驱逐逻辑使用DEBUG命令可能直接导致主线程卡死（见debug.c）架构师必备意识当看到的监控指标异常波动时，要能立即映射到源码中的对应操作任何Redis的"高性能"承诺，都要用fork延迟测试和大key压力测试验证最后警告。]]></description><category></category></item><item><title><![CDATA[微服务：常用网关对比]]></title><link>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145403451</link><guid>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145403451</guid><author>hrfhrf32101</author><pubDate>Fri, 31 Jan 2025 10:08:52 +0800</pubDate><description><![CDATA[建议采用双模架构：核心交易系统使用SCG保证高性能，边缘系统通过EdgeService实现协议适配，逐步向服务网格架构演进。注意：SCG代表spring cloud gateway。]]></description><category></category></item><item><title><![CDATA[微服务：主流断路器对比]]></title><link>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145395416</link><guid>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145395416</guid><author>hrfhrf32101</author><pubDate>Wed, 29 Jan 2025 21:51:37 +0800</pubDate><description><![CDATA[维度HystrixSentinelBizkeeper维护状态❌ 停止维护✅ 活跃（CNCF孵化）✅ 中等（华为云支持）动态规则静态配置动态配置（Nacos/ZK）依赖ServiceChain配置中心隔离策略线程池/信号量信号量信号量监控集成适用场景传统容错高并发流量治理ServiceComb生态集成最终建议新项目优先选择Sentinel（功能全面、云原生友好、社区活跃）。旧系统维护可暂时保留 Hystrix，但需规划迁移。华为云用户直接使用Bizkeeper，避免生态碎片化。]]></description><category></category></item><item><title><![CDATA[微服务：配置中心对比]]></title><link>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145394912</link><guid>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145394912</guid><author>hrfhrf32101</author><pubDate>Wed, 29 Jan 2025 20:46:46 +0800</pubDate><description><![CDATA[Config --> Git : 配置版本管理。Kie --> APISIX : 动态路由。Nacos --> DB : 持久化存储。component “配置中心” {cloud “基础设施层” {五、架构决策框架（ADM）]]></description><category></category></item><item><title><![CDATA[微服务：常用注册中心对比]]></title><link>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145389646</link><guid>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145389646</guid><author>hrfhrf32101</author><pubDate>Tue, 28 Jan 2025 23:42:05 +0800</pubDate><description><![CDATA[组件一致性模型健康检查通信协议动态配置适用场景NacosAP/CP 可选客户端心跳 + 服务端探测HTTP/gRPC支持微服务全链路（注册+配置）EurekaAP客户端心跳HTTP不支持Spring Cloud Netflix 生态ConsulCP主动探测 + TTLHTTP/DNS支持多数据中心、强一致性场景ZookeeperCP会话心跳TCP不支持Dubbo 生态、分布式协调CP心跳 + 自定义探活gRPC支持ServiceComb 生态、云原生架构。]]></description><category></category></item><item><title><![CDATA[注册中心核心时序图]]></title><link>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145389536</link><guid>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145389536</guid><author>hrfhrf32101</author><pubDate>Tue, 28 Jan 2025 23:25:52 +0800</pubDate><description><![CDATA[以下是使用。]]></description><category></category></item><item><title><![CDATA[微服务注册中心核心：CAP]]></title><link>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145389524</link><guid>https://blog.youkuaiyun.com/hrfhrf32101/article/details/145389524</guid><author>hrfhrf32101</author><pubDate>Tue, 28 Jan 2025 23:14:41 +0800</pubDate><description><![CDATA[以下是与。]]></description><category></category></item></channel></rss>