Apache ECharts

Overview

Apache ECharts was open-sourced by Baidu in 2013, entered the Apache Foundation in 2018 and became a top-level project, with long-term maintenance led from China. It is one of the few front-end developer tools rather than SaaS products in the BI & Visualization space, free and unhosted, embedded as a JavaScript library.

Its strengths are chart breadth and the Chinese-language ecosystem, with dozens of built-in types from line, bar, and pie to maps, graph, and Sankey, and an extremely rich option schema. Documentation and examples in Chinese are thorough, so domestic dashboard projects evaluate it first, and rendering switches between Canvas and SVG by data volume and interaction needs.

The limit is being a library rather than a platform, with no data source management, permissions, scheduling, or collaboration, so developers wire data and interactions themselves. The large option schema has a steep curve, and misconfiguration causes performance problems such as heavy scatter plots that are hard to localise.

Core Strengths

• Open-sourced in 2013 and a top-level Apache project since 2018, free under Apache 2.0 with no usage limits
• Dozens of built-in chart types covering maps, graphs, Sankey, and high-volume scatter
• Canvas and SVG rendering modes switchable to balance performance against interaction needs
• Thorough Chinese documentation and examples that domestic dashboards reuse directly

Product Ecosystem

Configuration and rendering

An option object declares axes, series, and interactions with Canvas or SVG rendering. For large datasets prefer Canvas with the large and progressive options enabled, or rendering stutters.

Maps and extension

Geographic coordinate systems and map components load GeoJSON for regional visualisation, and custom series plus extension packages are supported, though complex customisation means maintaining your own rendering logic and tests.

Drawbacks

• A front-end library only, leaving data sources, permissions, scheduling, and collaboration to build
• A large option schema with a steep curve where misconfiguration hides performance issues
• No built-in accessibility or print handling, requiring extra adaptation
• Occasional option changes between versions mean long-lived projects must track changelogs

Use Cases

• Data walls and operations dashboards (★★★★★) - Rich chart types plus Chinese docs make it the default for domestic screens
• Charts embedded in admin systems (★★★★★) - A library in your own front end without SaaS fees
• Reporting platforms needing governance (★★) - Permissions, scheduling, and collaboration belong to BI platforms
• Business analysis with no dev team (★) - Requires configuration and data wiring that non-technical teams cannot own

Pricing

The library is free and cost sits in development and upkeep. Do not compare it directly against a BI platform, since it answers how to draw interactive charts in a page rather than who can see which data, and the two are usually combined.

FAQ

• ECharts or a charting SaaS? ECharts for embedding in your own system with full control of style and interaction, and BI or SaaS reporting when business users need reports with managed permissions and scheduling.

• How do I fix lag with large data? Prefer Canvas with large and progressive enabled, reduce series count, and aggregate or downsample data. Rendering a hundred thousand points onto a shared instance will stutter regardless.

• Does it support server-side rendering? Node-side canvas rendering produces images or SVG for report exports and email. Configure fonts carefully or Chinese glyphs may be missing from exported images.