apache/shenyu

Apache ShenYu is a Java native API Gateway for service proxy, protocol conversion and API governance.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 39 minutes ago
Added to GitGenius on September 7th, 2026
Created on July 11th, 2018
Open Issues & Pull Requests: 556 (+0)
GitHub issues: Enabled
Number of forks: 3,066
Total Stargazers: 8,831 (+0)
Total Subscribers: 296 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.7 days
Mean response time: 22.0 days
90th percentile: 30.1 days
Tracked items: 485

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 96% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "type: question" is answered fastest, typically in about 23 hours, while "admin" waits about 4 weeks. Almost all tracked open issues have seen activity in the last three months. Only 4% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 421
New in 7 days: 5
Closed in 7 days: 57
Avg open age: 120 days
Stale 30+ days: 384
Stale 90+ days: 76

Recent activity

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

Top labels

  • type: bug (449)
  • priority: medium (212)
  • priority: high (137)
  • type: question (104)
  • admin (89)
  • status: volunteer wanted (75)
  • type: performance (57)
  • feature: plugin (32)

Detailed Description

Apache ShenYu is a Java native API Gateway that handles service proxy, protocol conversion, and API governance for microservice architectures.

The tool addresses the need for unified traffic management across heterogeneous microservice ecosystems. It works by sitting between clients and backend services, intercepting and routing requests while supporting multiple protocols and service frameworks. The gateway enables protocol conversion, allowing clients using one protocol to communicate with services using another, and provides centralized API governance capabilities for managing traffic policies, authentication, and service discovery across distributed systems.

Teams should adopt this tool when managing microservices built on diverse frameworks and protocols. It suits organizations running Dubbo, gRPC, HTTP, Spring Cloud, or SOFA services that need a single entry point for traffic management. The project is particularly valuable for teams requiring protocol bridging capabilities rather than simple HTTP routing, as it natively supports multiple service mesh technologies rather than treating them as afterthoughts.

The project maintains active development with regular commits across core gateway functionality, protocol adapters, and administrative tooling. Testing infrastructure is established with continuous integration workflows. The codebase shows ongoing refinement of the reactive Java implementation and expansion of supported backend protocols. Documentation is maintained in multiple languages, indicating sustained community engagement beyond a single region.