apache/linkis
Apache Linkis builds a computation middleware layer to facilitate connection, governance and orchestration between the upper applications and the underlying data engines. observed · 2026-08-28
Health v2 · maintenance only
71/100
- Activity 98
- Release rhythm 20
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: 281
- age_days: 2598
- days_rel: 320
- days_push: 14
- n_releases_24m: 2
Adoption not part of the score
3406 stars · 1168 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
Apache Linkis is a computation middleware layer that sits between upper-layer applications and underlying big data engines such as Spark, Hive, Presto, Flink, and JDBC databases. It exposes standardized REST, WebSocket, and JDBC interfaces for submitting and governing jobs, with unified resource sharing (variables, UDFs, scripts), task routing, load balancing, and multi-tenant resource control.
Use cases
- submit Spark or Hive jobs through a unified REST/JDBC gateway
- give multiple applications one entrance to many big data engines
- manage multi-tenant compute resource quotas and load balancing
- share UDFs, variables, and scripts across applications and engines
- route and orchestrate tasks across OLAP, OLTP, and streaming engines
- decouple applications from engine changes in a data platform
- run interactive SQL queries against Presto, Hive, or Trino via one API
When to choose
- you operate a big data platform with many engines and need a unified access layer
- you want standardized REST/JDBC/WS interfaces instead of direct engine connections
- you need multi-tenant resource governance, task routing, and audit controls
- you want to share user resources like UDFs and scripts across tools
When to avoid
- you only need a single engine connection - use the engine's native client or Livy directly
- you want a lightweight SQL client or BI tool rather than platform middleware
- your stack is not JVM/big-data oriented and the deployment overhead outweighs benefits
- you need a fully managed cloud service rather than self-hosted infrastructure
Facets
service · maturity stable
api-framework http-server rpc scheduling workflow-automation database middleware big-data databases backend apis microservices jvm self-hosted computation-middleware spark hive presto flink jdbc-gateway engine-orchestration multi-tenant resource-management scriptis job-execution data-engineering linux docker web-server
9 sources
- readme: https://github.com/apache/linkis · fetched 2026-08-28 · edb7a2d97b21
- homepage: https://linkis.apache.org/ · fetched 2026-08-29 · 54350c6f5878
- site_page: https://linkis.apache.org/docs/latest/about/introduction · fetched 2026-08-29 · 9bb896250b26
- site_page: https://linkis.apache.org/docs/1.7.0/about/introduction · fetched 2026-08-29 · dee10a92a2d1
- site_page: https://linkis.apache.org/docs/1.6.0/about/introduction · fetched 2026-08-29 · 6aa4df9665df
- site_page: https://linkis.apache.org/docs/1.5.0/about/introduction · fetched 2026-08-29 · 7fa5268afe65
- site_page: https://linkis.apache.org/docs/1.4.0/about/introduction · fetched 2026-08-29 · 69631d3f056e
- site_page: https://linkis.apache.org/docs/1.9.0/about/introduction · fetched 2026-08-29 · 8579b3df3ffb
- site_page: https://linkis.apache.org/faq/main · fetched 2026-08-29 · c395abe8e745
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| apache/linkis | main | 71 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem