Fellow，致力于推动 AI 和开源软件的采纳和开发者 体验。拥有超过十年的开发者关系、产品营销和开源生态构建的经验， 曾在 Google 负责多个开发技术的深度推广和社区建设，包括 Android、Flutter 和 TensorFlow 等。他坚信开源是推动技术进步和 开发者成长的关键步骤，希望有更多人参与开源和社区共建。 25 / 111 开源模型未必更先进，但会更长久 文/顾钧 “开源”是指采用符合 具价值专家（TVP）、微软技术俱乐部（苏州）主席，苏州市人工智能 学会理事，机械工业出版社专家委员会委员，江苏省司法厅电子数据鉴 定人。《网站模块化开发全程实录》《微信开发深度解析》图书作者， Senparc.Weixin SDK 等开源项目作者，盛派开发者社区发起人。 56 / 111 2024 年 AI 编程工具的进化 文/黄峰达 与 2023 年相比，2024 年 AI 在软件工程中的应用已经变得更加广泛和深入。这一趋势体现 多新功能，如认证 和访问控制。 在代理应用中，记忆管理同样关键。开源项目 Mem0 将记忆分为短期记忆和长期记忆，后 者进一步细分为事件记忆、语义记忆和程序记忆，并基于此抽象出一套记忆管理 SDK。Zep 通 过时态知识图谱管理和更新用户信息，跟踪事实变化并提供最新数据线索。MemGPT 借鉴了计 64 / 111 算机操作系统内存管理机制，模拟虚拟内存工作原理，构建了一套记忆管理系统。这些项目使

架构 < 18 用户层  OpenAPI：暴露标准 Rest 风格 HTTP 接口，简单易用，方便多语言集成。  Console：易用控制台，做服务管理、配置管理等操作。  SDK：多语言 SDK，目前几乎支持所有主流编程语言。  Agent：Sidecar 模式运行，通过标准 DNS 协议与业务解耦。  CLI：命令行对产品进行轻量化管理，像 git ⼀样好用。 业务层 插件机制：实现三个模块可分可合能力，实现扩展点 SPI 机制，用于扩展自己公司定制。  事件机制：实现异步化事件通知，SDK 数据变化异步通知等逻辑，是 Nacos 高性能的关键部分。  日志模块：管理日志分类，日志级别，日志可移植性（尤其避免冲突），日志格式，异常码+帮 助文档。  回调机制：SDK 通知数据，通过统⼀的模式回调用户处理。接口和数据结构需要具备可扩展性。  寻址模式：解决 Server Server IP 直连，域名访问，Nameserver 寻址、广播等多种寻址模式，需要可 扩展。  推送通道：解决 Server 与存储、Server 间、Server 与 SDK 间高效通信问题。  容量管理：管理每个租户，分组下的容量，防止存储被写爆，影响服务可用性。  流量管理：按照租户，分组等多个维度对请求频率，长链接个数，报文大小，请求流控进行控制。  缓存机制：容灾目录，本地缓存，Server

VirtualBox comes with comprehensive support for third-party developers. This Software Devel- opment Kit (SDK) contains all the documentation and interface files that are needed to write code that interacts with currently in the process of being added to VirtualBox. What is primarily of interest for purposes of the SDK is the API layer block that sits on top of all the previously mentioned blocks. This API, which we exposes the entire feature set of the virtualization engine below. It is completely documented in this SDK Reference – see chapter 5, Classes (interfaces), page 50 and chapter 6, Enumerations (enums), page

VirtualBox comes with comprehensive support for third-party developers. This Software Devel- opment Kit (SDK) contains all the documentation and interface files that are needed to write code that interacts with currently in the process of being added to VirtualBox. What is primarily of interest for purposes of the SDK is the API layer block that sits on top of all the previously mentioned blocks. This API, which we exposes the entire feature set of the virtualization engine below. It is completely documented in this SDK Reference – see chapter 5, Classes (interfaces), page 50 and chapter 6, Enumerations (enums), page

VirtualBox comes with comprehensive support for third-party developers. This Software Devel- opment Kit (SDK) contains all the documentation and interface files that are needed to write code that interacts with currently in the process of being added to VirtualBox. What is primarily of interest for purposes of the SDK is the API layer block that sits on top of all the previously mentioned blocks. This API, which we exposes the entire feature set of the virtualization engine below. It is completely documented in this SDK Reference – see chapter 5, Classes (interfaces), page 52 and chapter 6, Enumerations (enums), page

VirtualBox comes with comprehensive support for third-party developers. This Software Devel- opment Kit (SDK) contains all the documentation and interface files that are needed to write code that interacts with currently in the process of being added to VirtualBox. What is primarily of interest for purposes of the SDK is the API layer block that sits on top of all the previously mentioned blocks. This API, which we exposes the entire feature set of the virtualization engine below. It is completely documented in this SDK Reference – see chapter 5, Classes (interfaces), page 52 and chapter 6, Enumerations (enums), page

VirtualBox comes with comprehensive support for third-party developers. This Software Devel- opment Kit (SDK) contains all the documentation and interface files that are needed to write code that interacts with currently in the process of being added to VirtualBox. What is primarily of interest for purposes of the SDK is the API layer block that sits on top of all the previously mentioned blocks. This API, which we exposes the entire feature set of the virtualization engine below. It is completely documented in this SDK Reference – see chapter 5, Classes (interfaces), page 44 and chapter 6, Enumerations (enums), page

VirtualBox comes with comprehensive support for third-party developers. This Software Devel- opment Kit (SDK) contains all the documentation and interface files that are needed to write code that interacts with currently in the process of being added to VirtualBox. What is primarily of interest for purposes of the SDK is the API layer block that sits on top of all the previously mentioned blocks. This API, which we exposes the entire feature set of the virtualization engine below. It is completely documented in this SDK Reference – see chapter 5, Classes (interfaces), page 44 and chapter 6, Enumerations (enums), page

RAM, more disk capacity • Moving data into and out of RAM • File IO in C++ from fstream to the OS SDK • The 64-bit address spaceSUB-MEGABYTE DAYS • Why do we have files?SUB- MEGABYTE DAYSSUB- MEGABYTE FROM FSTREAM TO THE OS SDK constexpr size_t buf_size = 4096u; char buf[buf_size]; ifstream file(“huge_log.txt”); file.read(buf, buf_size);FILE IO IN C++ FROM FSTREAM TO THE OS SDK constexpr size_t buf_size f = fopen(“huge_log.txt”, “r”); fread(buf, 1, buf_size, f);FILE IO IN C++ FROM FSTREAM TO THE OS SDK constexpr size_t buf_size = 4096u; char buf[buf_size]; HANDLE file = CreateFile(“huge_log.txt”

业务逻辑 SDK 协议编解码 服务发现 负载均衡 熔断限流 服务路由 …… 混合在一个进程内， 应用既有业务逻辑， 也有各种功能， 每次升级都要重新发布应用 升级成本高 版本碎片化严重 中间件演进困难6/39 微服务治理与业务逻辑解耦 Part 1： 为什么需要Service Mesh? Service 业务逻辑 SDK 协议编解码 熔断限流 服务路由 …… Service 业务逻辑 轻量级 SDK 协议编解码 Sidecar （MOSN） + 服务发现 负载均衡 熔断限流 服务路由 …… - 专注业务实现 - 无需感知Mesh - 专注服务间通讯和相 关能力 - 与业务逻辑无关 将SDK客户端 的功能剥离 混合在一个进程内， 应用既有业务逻辑， 也有各种功能， 也有各种功能， 每次升级都要重新发布应用 业务进程专注于业务逻辑 SDK 中的大部分功能， 拆解为独立进程， 以 Sidecar 的模式运行 将服务治理能力下沉到基础设施，实现独立演进，透明升级7/39 异构系统统一治理 Part 1： 为什么需要Service Mesh? 多语言、多协议 图片来源：https://www.redhat.com/en/topic