apache/linkis

Apache Linkis builds a computation middleware layer to facilitate connection, governance and orchestration between the upper applications and the underlying...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 14 minutes ago
Added to GitGenius on September 20th, 2026
Created on July 23rd, 2019
Open Issues & Pull Requests: 177 (+0)
GitHub issues: Enabled
Number of forks: 1,168
Total Stargazers: 3,413 (+0)
Total Subscribers: 261 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 46
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 463 days
Stale 30+ days: 36
Stale 90+ days: 36

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • feature (42)
  • bug (25)
  • Question (11)
  • type=NewFeature (4)
  • 1.3.2 (3)
  • part3 (3)
  • easy to fix (1)
  • enhancement (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Apache Linkis is a computation middleware layer that facilitates connection, governance, and orchestration between upper applications and underlying data engines.

Linkis solves the problem of complex integration between applications and multiple data processing engines by providing a standardized abstraction layer. Rather than having applications communicate directly with each engine, Linkis intercepts these interactions through standard interfaces including REST, WebSocket, and JDBC. This approach decouples the application layer from the engine layer, reducing network complexity and simplifying maintenance. The middleware also enables resource sharing across engines, including unified variables, scripts, user-defined functions, and resource files.

Organizations should adopt Linkis when they operate multiple data engines such as Spark, Hive, Presto, Flink, or MySQL and want to avoid building custom integration logic for each combination. It suits environments where applications need to submit jobs to different engines without being tightly coupled to their specific APIs or protocols. The tool is particularly valuable in enterprises managing diverse data processing workloads that require consistent governance and resource management across platforms.

The project maintains active development with regular contributions across its core components. The codebase shows ongoing work on engine connectors, resource management systems, and the REST API layer. Development activity spans multiple functional areas including the application manager, context service, and job server components, indicating sustained effort to expand engine support and improve orchestration capabilities.