knative/eventing

Event-driven application platform for Kubernetes

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 11 minutes ago
Added to GitGenius on April 8th, 2021
Created on March 12th, 2018
Open Issues & Pull Requests: 100 (+0)
Number of forks: 635
Total Stargazers: 1,552 (+0)
Total Subscribers: 30 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.2 days
Mean response time: 127.0 days
90th percentile: 312.6 days
Tracked items: 211

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 66% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "kind/bug" is answered fastest, typically in about 32 hours, while "kind/feature-request" waits about 2 weeks. Only 8% of issues opened in the past year have been closed. Three people close 66% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 106
New in 7 days: 22
Closed in 7 days: 3
Avg open age: 811 days
Stale 30+ days: 81
Stale 90+ days: 74

Recent activity

Opened in 7 days: 22
Closed in 7 days: 1
Comments in 7 days: 22
Events in 7 days: 92

Top labels

  • auto:flaky (1,528)
  • kind/feature-request (791)
  • kind/bug (708)
  • lifecycle/stale (337)
  • triage/accepted (245)
  • area/test-and-release (241)
  • priority/important-soon (209)
  • help wanted (175)

Detailed Description

Knative Eventing is an event-driven application platform for Kubernetes that enables asynchronous application development through event delivery from any source. Written primarily in Go, the project provides a collection of APIs designed to facilitate event-driven architectures by routing events from producers, known as sources, to consumers, known as sinks. The platform operates as a standalone system that supports various workload types, including standard Kubernetes Services and Knative Serving Services, making it flexible for different deployment scenarios.

The core functionality of Knative Eventing centers on loose coupling between services during development and deployment. A defining characteristic is that event producers can generate events before consumers are actively listening, and conversely, consumers can express interest in event classes before those events are being produced. This decoupling enables services to be connected into new applications without requiring modifications to either producers or consumers, and allows selection of specific event subsets from particular producers.

Knative Eventing implements event routing using standard HTTP requests and adheres to the CloudEvents specification, a CNCF standard with broad support across programming languages. This standards-based approach simplifies the creation, understanding, transmission, and reception of events across diverse environments. The platform's components are intentionally designed to be loosely coupled, allowing independent development and deployment of individual elements.

The repository demonstrates significant community engagement and active maintenance.

The classification data reveals that Knative Eventing addresses multiple aspects of event-driven architecture including event channels, message routing, event sources, reliable delivery, event brokers, asynchronous processing, and observability within Kubernetes environments.

The high-level mission articulated in the repository is to enable asynchronous application development through event delivery from anywhere, reflecting the platform's ambition to serve as a comprehensive solution for event-driven workloads in cloud-native contexts. The project maintains comprehensive documentation and actively encourages contributions through identified ready-to-work issues and detailed contribution guidelines, with users directed to the knative-users forum for community engagement and support.