Route 特点： • 干掉形式上的网关 • 轻路由前置到 LB • 业务集成网关 Jar • 业务之间互不干扰 • NodeJS 版 缺点： • 接入困难（几十个 jar 依赖） • Jar 包冲突 • 升级困难 • 版本离散 • NodeJS 版本维护成本高 30+系统、70-80%流量11/21 Mesh 化网关架构（2018-2019) APP Mesh 化网关架构

方案 FAAS 实践进展20/25 Knative 基本实践数据 FAAS 实践进展 分享主题：字号 分享嘉宾 平均冷启动时间 不包含 Istio-proxy 业务为 go 语言或 nodejs 语言的简单接口 3.6 秒 额外内存占用 30~60 MB 为 queue-proxy 占用21/25 踩过的坑/问题 FAAS 实践进展 • 镜像源问题 • RevisionUnkown

增加成本调用及部署成本，高于所获得 的收益，价值难以兑现。 2. 针对服务化架构并未带来新的突破，将已有功能换个 地方重复造轮子。阿里巴巴曾属于第二种原因有……重复运维，多语言支持困境 NodeJS Java C++ Golang 运维系统云原生时代快速赋能 Biz APP Non Ali Biz框架思维转向平面思维 Service Mesh Biz Non Ali Biz将中间件能力下层到基础层

MOA 1.0微服务体系整体架构 注册中心 • Redis作为底层存储 • 跨语言地址发现服务Lookup • 中心化存活检测 多语言支持 • Java、PHP、Python、Go、NodeJs • Redis传输协议 / 复用Redis客户端 • 服务发布Proxy / 并行调用Proxy 服务治理 • 服务治理平台、配置中心 • 监控、日志、分布式跟踪 • 异步调用、压测7/24

• 更多：https://apisix.apache.org 云 原 ⽣ 社 区 M e e t u p 第 四 期 · ⼴ 州 站 • 多语⾔⽀持 • Java • Golang • NodeJS • JS • Rust • Others … 云 原 ⽣ 社 区 M e e t u p 第 四 期 · ⼴ 州 站 APISIX 定位 云 原 ⽣ 社 区 M e e t

Ø运维体系的有力支撑 • LDC • 弹性伸缩 • 蓝绿/容灾/.. Ø金融级网络安全 • 金融级鉴权体系 • 云原生zero trust网络安全趋势 Ø异构语言体系融合 • SOFA/NodeJS/C++/Python/.. • 业务低成本融入服务，运维体系为什么要自研Golang版本ServiceMesh 2 Ø跨团队协作需要考虑技术栈落地成本 ü 参与团队分别使用C，Golang，Java等多种技术栈

functionality to receive notifications from the operating system (e.g. via inotify on Linux). See the NodeJS documentation linked below for details. The returned value is an object with boolean fields renamed watching the file. This behavior of this function varies slightly across platforms. See https://nodejs.org/api/fs.html#fs_caveats for more detailed information. This is a thin wrapper over calling wait functionality to receive notifications from the operating system (e.g. via inotify on Linux). See the NodeJS documen- tation linked below for details. This will continuing tracking changes for path in the

functionality to receive notifications from the operating system (e.g. via inotify on Linux). See the NodeJS documentation linked below for details. The returned value is an object with boolean fields renamed watching the file. This behavior of this function varies slightly across platforms. See https://nodejs.org/api/fs.html#fs_caveats for more detailed information. This is a thin wrapper over calling wait functionality to receive notifications from the operating system (e.g. via inotify on Linux). See the NodeJS documen- tation linked below for details. This will continuing tracking changes for path in the

functionality to receive notifications from the operating system (e.g. via inotify on Linux). See the NodeJS documentation linked below for details. The returned value is an object with boolean fields renamed watching the file. This behavior of this function varies slightly across platforms. See https://nodejs.org/api/fs.html#fs_caveats for more detailed information. This is a thin wrapper over calling wait functionality to receive notifications from the operating system (e.g. via inotify on Linux). See the NodeJS documen- tation linked below for details. This will continuing tracking changes for path in the

functionality to receive notifications from the operating system (e.g. via inotify on Linux). See the NodeJS documentation linked below for details. The returned value is an object with boolean fields renamed watching the file. This behavior of this function varies slightly across platforms. See https://nodejs.org/api/fs.html#fs_caveats for more detailed information. This is a thin wrapper over calling wait functionality to receive notifications from the operating system (e.g. via inotify on Linux). See the NodeJS documen- tation linked below for details. This will continuing tracking changes for path in the