This is an automated email from the ASF dual-hosted git repository.
wusheng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/skywalking-website.git
The following commit(s) were added to refs/heads/master by this push:
new d22d3b92c3d Update graphs.
d22d3b92c3d is described below
commit d22d3b92c3dac89584b8a589d7ef8375ed49b290
Author: Wu Sheng <[email protected]>
AuthorDate: Mon Mar 16 08:11:47 2026 +0800
Update graphs.
---
.../graph.jpg | Bin 0 -> 49994 bytes
.../index.md | 2 ++
.../index.md | 4 ++--
.../graph.jpg | Bin 0 -> 49994 bytes
.../index.md | 2 ++
.../index.md | 4 ++--
6 files changed, 8 insertions(+), 4 deletions(-)
diff --git
a/content/blog/2026-03-13-how-ai-changed-the-economics-of-architecture/graph.jpg
b/content/blog/2026-03-13-how-ai-changed-the-economics-of-architecture/graph.jpg
new file mode 100644
index 00000000000..e640a21acb9
Binary files /dev/null and
b/content/blog/2026-03-13-how-ai-changed-the-economics-of-architecture/graph.jpg
differ
diff --git
a/content/blog/2026-03-13-how-ai-changed-the-economics-of-architecture/index.md
b/content/blog/2026-03-13-how-ai-changed-the-economics-of-architecture/index.md
index 3014846770d..7de63a6bd35 100644
---
a/content/blog/2026-03-13-how-ai-changed-the-economics-of-architecture/index.md
+++
b/content/blog/2026-03-13-how-ai-changed-the-economics-of-architecture/index.md
@@ -15,6 +15,8 @@ tags:
*SkyWalking GraalVM Distro: A case study in turning runnable PoCs into a
repeatable migration pipeline.*
+
+
The most important lesson from this project is not that AI can generate a
large amount of code. It is that AI changes the economics of architecture. When
runnable PoCs become cheap to build, compare, discard, and rebuild, architects
can push further toward the design they actually want instead of stopping early
at a compromise they can afford to implement.
That shift matters a lot in mature open source systems. Apache SkyWalking OAP
has long been a powerful and production-proven observability backend, but it
also carries all the realities of a large Java platform: runtime bytecode
generation, reflection-heavy initialization, classpath scanning, SPI-based
module wiring, and dynamic DSL execution that are friendly to extensibility but
hostile to GraalVM native image.
diff --git
a/content/blog/2026-03-13-skywalking-graalvm-distro-design-and-benchmarks/index.md
b/content/blog/2026-03-13-skywalking-graalvm-distro-design-and-benchmarks/index.md
index 613ff35f027..d0f343461aa 100644
---
a/content/blog/2026-03-13-skywalking-graalvm-distro-design-and-benchmarks/index.md
+++
b/content/blog/2026-03-13-skywalking-graalvm-distro-design-and-benchmarks/index.md
@@ -12,10 +12,10 @@ tags:
- BanyanDB
---
-
-
*A technical deep-dive into how we migrated Apache SkyWalking OAP to GraalVM
Native Image — not as a one-off port, but as a repeatable pipeline that stays
aligned with upstream.*
+
+
For the broader story of how AI engineering made this project economically
viable, see [How AI Changed the Economics of
Architecture](/blog/2026-03-13-how-ai-changed-the-economics-of-architecture/).
## Why GraalVM Is Not Optional
diff --git
a/content/zh/2026-03-13-how-ai-changed-the-economics-of-architecture/graph.jpg
b/content/zh/2026-03-13-how-ai-changed-the-economics-of-architecture/graph.jpg
new file mode 100644
index 00000000000..e640a21acb9
Binary files /dev/null and
b/content/zh/2026-03-13-how-ai-changed-the-economics-of-architecture/graph.jpg
differ
diff --git
a/content/zh/2026-03-13-how-ai-changed-the-economics-of-architecture/index.md
b/content/zh/2026-03-13-how-ai-changed-the-economics-of-architecture/index.md
index eb6f8ea31bf..cd8ad44c2ac 100644
---
a/content/zh/2026-03-13-how-ai-changed-the-economics-of-architecture/index.md
+++
b/content/zh/2026-03-13-how-ai-changed-the-economics-of-architecture/index.md
@@ -15,6 +15,8 @@ tags:
*以 SkyWalking GraalVM Distro 为例，看 AI Coding 如何把一批探索性 PoC 打磨成一条可重复的迁移流水线。*
+
+
这个项目给我最大的启发，不是 AI 能写多少代码，而是 AI Coding 改变了架构设计的试错成本。当一个想法可以很快做成
PoC、跑起来验证、不行就推翻重来时，架构师就更有机会逼近自己真正想要的设计，而不是过早停在“团队现在做得出来”的折中方案上。
这种变化在成熟开源系统里尤其重要。Apache SkyWalking OAP 长期以来一直是一个功能强大且经过生产验证的可观测性后端，但大型 Java
平台该有的问题它一个不少：运行时字节码生成、重反射初始化、classpath 扫描、基于 SPI 的模块装配，以及动态 DSL 执行——这些机制方便扩展，但做
GraalVM Native Image 时全是障碍。
diff --git
a/content/zh/2026-03-13-skywalking-graalvm-distro-design-and-benchmarks/index.md
b/content/zh/2026-03-13-skywalking-graalvm-distro-design-and-benchmarks/index.md
index 0583db75982..8b08a730533 100644
---
a/content/zh/2026-03-13-skywalking-graalvm-distro-design-and-benchmarks/index.md
+++
b/content/zh/2026-03-13-skywalking-graalvm-distro-design-and-benchmarks/index.md
@@ -12,10 +12,10 @@ tags:
- BanyanDB
---
-
-
*这篇文章会完整介绍我们如何把 Apache SkyWalking OAP 迁移到 GraalVM Native
Image。目标不是做一次性移植，而是把这件事做成一套能持续跟上上游演进的流程。*
+
+
如果你想看这项工作的更大背景，以及 AI Coding 如何让这个项目真正做得出来，请阅读：[AI Coding
如何重塑软件架构师的工作方式](/zh/2026-03-13-how-ai-changed-the-economics-of-architecture/)。
## 为什么 GraalVM 在这里是刚需
