3 ms·

It has built-in integrations so you don't have to standup a service or API Gateway to receive webhooks from their list of partners. Their initial list of partne

It has built-in integrations so you don't have to standup a service or API Gateway to receive webhooks from their list of partners. Their initial list of partners is [1]: - Datadog - OneLogin - Pagerduty - Saviynt - Segment - SignalFx - SugarCRM - Symantec - Whispir - Zendesk and of course that'll grow over time - anyone that produces events can become a partner. [1]: https://aws.amazon.com/eventbridge/partners/ https://aws.amazon.com/eventbridge/partners/

chrsstrm 7y ago
So kind of an IFTT or Zapier piped directly into your AWS backend?
- zianwar 7y ago
  Yeah, I also thought of IFTT when I saw this: https://ifttt.com/services https://ifttt.com/services
unixhero 7y ago
Eek! Missing Salesforce!!!
zmmmmm 7y ago
Reminds me a bit of Apache Camel then - let's you easily route end points from all kinds of different protocols as if they are messages.
- vips7L 7y ago
  Maybe I never looked at it hard enough, but I couls never figure out what Camel was for.
  - jungturk 7y ago
    Camel was libraries that codified the the Enterprise Integration Patterns (https://www.enterpriseintegrationpatterns.com/ https://www.enterpriseintegrationpatterns.com/ - channels, messages, service activators, etc...) that allowed you to code against the abstractions rather than the underlying implementations (JMS w/ topics & queues, AMQP w/ exchanges, etc..) Spring offered a competing set of libs with Spring Integration. Those we mostly just libraries, though, so you have something running under them for distribution (like a message broker or service bus or, these days, a cloud managed service).
    - zmmmmm 7y ago
      > so you have something running under them for distribution (like a message broker or service bus or, these days, a cloud managed service). Actually Apache Camel doesn't really care if you have a message broker or not. You can set it up without one and still use half its functionality. (eg: connect a file arriving in a dropbox account to an outbound SMTP etc).
  - zmmmmm 7y ago
    It's one of those things that you don't know you need ... until you get half way to re-inventing it yourself and then you realise you needed it. Wrt this, probably the more relevant part is all the end point integrations: https://camel.apache.org/components.html https://camel.apache.org/components.html So it makes it super easy to, say, connect an inbound email to an ftp server so that all the messages get saved as files.

chrsstrm 7y ago

So kind of an IFTT or Zapier piped directly into your AWS backend?

zianwar 7y ago
Yeah, I also thought of IFTT when I saw this: https://ifttt.com/services https://ifttt.com/services

unixhero 7y ago

Eek! Missing Salesforce!!!

zmmmmm 7y ago

Reminds me a bit of Apache Camel then - let's you easily route end points from all kinds of different protocols as if they are messages.

vips7L 7y ago
Maybe I never looked at it hard enough, but I couls never figure out what Camel was for.
- jungturk 7y ago
  Camel was libraries that codified the the Enterprise Integration Patterns (https://www.enterpriseintegrationpatterns.com/ https://www.enterpriseintegrationpatterns.com/ - channels, messages, service activators, etc...) that allowed you to code against the abstractions rather than the underlying implementations (JMS w/ topics & queues, AMQP w/ exchanges, etc..) Spring offered a competing set of libs with Spring Integration. Those we mostly just libraries, though, so you have something running under them for distribution (like a message broker or service bus or, these days, a cloud managed service).
  - zmmmmm 7y ago
    > so you have something running under them for distribution (like a message broker or service bus or, these days, a cloud managed service). Actually Apache Camel doesn't really care if you have a message broker or not. You can set it up without one and still use half its functionality. (eg: connect a file arriving in a dropbox account to an outbound SMTP etc).
- zmmmmm 7y ago
  It's one of those things that you don't know you need ... until you get half way to re-inventing it yourself and then you realise you needed it. Wrt this, probably the more relevant part is all the end point integrations: https://camel.apache.org/components.html https://camel.apache.org/components.html So it makes it super easy to, say, connect an inbound email to an ftp server so that all the messages get saved as files.