Microsoft Clarity vs Apache SkyWalking

Apache SkyWalking is an open-source APM and observability platform, and its recent releases have been a sustained rebuild of its own foundations. BanyanDB, its purpose-built storage engine, replaced H2 outright and was then declared large-scale ready. The Groovy DSL runtime was ripped out for an ANTLR4 and Javassist pipeline with fail-fast compilation. GenAI observability arrived as a new telemetry domain. Version 11.0.0 now removes the bundled UI from the OAP release entirely, adds TLS with certificate hot-reload across every HTTP surface, and introduces a queryAlarms GraphQL API alongside runtime rule hot-update and a live DSL debugger.

The consistent method is subtraction: remove the convenient default, absorb the dependency into something the project controls, then optimise it. H2 went so BanyanDB could be the only answer. Groovy went so the DSL could be compiled and type-checked. Now the UI goes so the backend can release on its own cadence. Each removal costs operators a migration and buys the project a surface it fully owns. The security and operations work in 11.0.0 — TLS everywhere, cert rotation without restart, alarm querying by entity and layer — reads as the same platform being made deployable in environments that audit these things.

With the UI decoupled and released independently, the version coupling operators previously relied on is gone; expect the project to publish compatibility guidance or a supported-version matrix between OAP and Horizon UI, since the release notes acknowledge there is no 1:1 mapping.