8 | A model for event interoperability between event producers and their consumers
9 | to favor better developer experience, robust integration, and infrastructural
10 | efficiency.
11 |
12 |
13 |
14 |
15 |
What are Event Destinations?
16 |
17 | Event Destinations are endpoints where event producers, such as API Platforms
18 | and SaaS, deliver events. Examples of destination types include AWS SQS, GCP
19 | Pub/Sub, Hookdeck Event Gateway, RabbitMQ, Amazon EventBridge, Kafka,
20 | Webhooks, and more.
21 |
4 | Contribute the the Event Destinations Initiative by providing feedback on the
5 | guidelines within the specification, submitting other examples of
6 | implementations, or sharing your support for the initiative.
7 |
70 |
71 |
76 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # Event Destinations Initiative
2 |
3 | An initiative to support a new model for event interoperability between event producers and their consumers to favor better developer experience, robust integration, and infrastructural efficiency.
4 |
5 | 
6 |
7 | ## What are Event Destinations
8 |
9 | Event Destinations expand the capabilities of event producers and benefit event consumers by providing more efficient, reliable, and flexible event delivery options. Event Destinations champion a range of event destinations types beyond just traditional webhooks, allowing developers to use the tools they are most familiar with.
10 |
11 | Event Destinations are endpoints or systems to which event producers can send events and give the developer the choice to use the tools they are familiar with directly. For example:
12 |
13 | - Google Cloud Pub/Sub
14 | - AWS SQS
15 | - Hookdeck Event Gateway
16 | - Amazon EventBridge
17 | - Kafka
18 | - RabbitMQ
19 | - And, of course, traditional HTTP webhooks
20 |
21 | Event Destinations benefit event producers and event consumers.
22 |
23 | For event producers:
24 |
25 | - **Efficiency gains**: Reduced failure rates and retried deliveries compared to public HTTP endpoints. Unlock improved performance for high-throughput scenarios.
26 | - **Protocol flexibility**: Leverage more efficient protocols and encodings.
27 | - **Cost & resource efficient**: Smart retry logic, improved deliverability and scalable infrastructure minimize resource consumption, reducing operational costs while ensuring seamless event delivery at any scale.
28 |
29 | For event consumers:
30 |
31 | - **Streamlined infrastructure and operations**: Eliminate the need for API gateways, load balancers, HTTP consumers, and other infrastructure components, reducing maintenance overhead.
32 | - **Reduced developer burden**: Receive events directly to existing or preferred infrastructure and make use of existing and familiar ecosystem tooling.
33 | - **Predictable behavior**: Standardize event expectations—the message bus handles timeouts, retries, and security.
34 |
35 | ## Event Destinations Specification
36 |
37 | The latest draft version of the specification is in [specification.md](specification.md).
38 |
39 | ## Get Involved
40 |
41 | Read [CONTRIBUTING.md](CONTRIBUTING.md) to learn how to contribute to this repository.
42 |
43 | We use GitHub Discussions for:
44 |
45 | - [General discussions](https://github.com/hookdeck/event-destinations/discussions/new?category=ideas)
46 | - [New ideas](https://github.com/hookdeck/event-destinations/discussions/new?category=ideas)
47 | - [Q&A](https://github.com/hookdeck/event-destinations/discussions/new?category=q-a)
48 |
49 | ## Related Initiatives
50 |
51 | - [Async API](https://www.asyncapi.com)
52 | - [CloudEvents](https://cloudevents.io/)
53 | - [Webhook standardization projects](https://webhooks.fyi/learn-more/standards)
54 |
55 | ## Learn More
56 |
57 | Visit the [Event Destinations Initiative website](https://eventdestinations.org) to learn more.
--------------------------------------------------------------------------------
/website/src/pages/index.astro:
--------------------------------------------------------------------------------
1 | ---
2 | import "../global.scss";
3 | import Title from "../components/Title.astro";
4 | import Nav from "../components/Nav.astro";
5 | import Head from "../components/Head.astro";
6 | import Implementations from "../components/Implementations.astro";
7 | import Manifesto from "../components/Manifesto.astro";
8 | import Supporters from "../components/Supporters.astro";
9 | import Guidelines from "../components/Guidelines.astro";
10 | import Contribute from "../components/Contribute.astro";
11 |
12 | const title = "Event Destinations Initiative";
13 | const description =
14 | "A model for event interoperability between event producers and their consumers to favor better developer experience, robust integration, and infrastructural efficiency";
15 | const tags = [
16 | "event destinations",
17 | "send webhooks",
18 | "event delivery",
19 | "event destinations",
20 | "event platform",
21 | ];
22 | ---
23 |
24 |
25 |
26 |