https://github.com/rootfs/eventing-1
Open source specification and implementation of Knative event binding and delivery
https://github.com/rootfs/eventing-1
Last synced: 4 months ago
JSON representation
Open source specification and implementation of Knative event binding and delivery
- Host: GitHub
- URL: https://github.com/rootfs/eventing-1
- Owner: rootfs
- License: apache-2.0
- Created: 2018-06-06T16:49:08.000Z (about 7 years ago)
- Default Branch: master
- Last Pushed: 2018-08-07T19:53:11.000Z (almost 7 years ago)
- Last Synced: 2024-12-29T21:23:02.306Z (5 months ago)
- Language: Go
- Homepage:
- Size: 14.8 MB
- Stars: 0
- Watchers: 5
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Roadmap: roadmap.md
Awesome Lists containing this project
README
# Eventing
This repo contains a work-in-progress eventing system that is designed to
address a common need for cloud native development:
1. Services are loosely coupled during development and deployed independently
2. A producer can generate events before a consumer is listening, and a consumer
can express an interest in an event or class of events that is not yet being
produced.
3. Services can be connected to create new applications
- without modifying producer or consumer.
- with the ability to select a specific subset of events from a particular
producer
The above concerns are consistent with the [design goals](https://github.com/cloudevents/spec/blob/master/spec.md#design-goals) of CloudEvents, a common specification for cross-service interoperability being developed by the CNCF Serverless WG.
## System design notes
We’re following an agile process, starting from a working prototype that
addresses a single use case and iterating to support additional use cases.
This repo depends on [knative/serving](https://github.com/knative/serving) and
together with [knative/build](https://github.com/knative/build) provides a
complete serverless platform.
The primary goal of *eventing* is interoperabilty; therefore, we expect to
provide common libraries that can be used in other systems to emit or consume
events.
## Naming
We'll be tracking the CloudEvents nomenclature as much as possible; however,
that is in flux and many of the needed terms are outside of the current scope
of the specification. At the moment, in our code and documentation, we may use
the terms "binding" and "flow" at different times to represent the concept of
attaching an event (or filtered event stream via a "trigger) to an action.
# Getting Started
* [Setup Knative](https://github.com/knative/serving)
* [Setup Binding](./DEVELOPMENT.md)
* [Run samples](./sample/README.md)