How NvWa Boosts Development Efficiency: Architecture, Plugins, and Unified Models

What Is NvWa

NvWa is a one‑stop platform that allows developers, testers, and operators to inject technical capabilities such as caching, fallback, mock, and gray release into running code without modifying source files, thereby enhancing development efficiency.

Evolution of NvWa

Version 1.0 focused on performance and stability, providing plug‑ins for fallback, caching, and flow control. Version 2.0 introduced a graphical console for configuration, and Version 3.0 expanded NvWa into a full‑featured toolbox covering the entire development process.

Efficiency Scenarios

Development: cache, fallback, gray release, dynamic logging.

Testing: mock, automated tests, performance testing.

Operations: traffic tracing, flow control, replay, robot orchestration.

Architecture Overview

NvWa consists of an SDK, a control console, and multiple plug‑ins. It uses AOP‑style dynamic proxies to intercept method calls (cut points) and apply plug‑ins (handlers) that execute solution executors and component executors.

Plugin System

Each plug‑in implements a handle method, while solution executors provide preHandle, afterHandle, and aroundHandle APIs. Component executors form a tree of reusable elements, some with lifecycle management (e.g., timed activation).

Unified Models

Three models are unified: a message model for internal processing, a configuration model for front‑end forms, and a storage model for persistence. The unified message model reduces code duplication, while the configuration model is trimmed, flattened, mapped, grouped, and ordered for user‑friendly UI rendering.

Process Flow

The flow includes plug‑in registration, configuration listening, handler construction, and runtime proxy execution. State machines manage versioning and environment promotion, ensuring safe releases.

UI Integration

The front‑end uses the Lego 3.0 low‑code platform to render unified configuration pages, dynamic forms, and monitoring dashboards. Permissions are handled via BUC, ACL, and AONE services.

Data Bridge

NvWa connects to various data sources (SLS, Lindorm, Tair, MySQL, files) and pipelines (Sunfire monitoring, Blink streaming, ODPS storage, FBI reporting, DingTalk alerts) to provide end‑to‑end observability and troubleshooting.