Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Thanks for your reply Robin! I agree with you but do you think dogfooding webhooks is common/good practice? Feels clumsy to me. This is really what's at the heart of my hesitation. Commented Sep 12, 2018 at 2:07
  • We have abstracted helper functions for 'services' (e.g. get-events) and 'system events' (SNS) which load up 'queues' (SQS) that invoke 'services' (Lambda). Seems a shame to ignore this wonderful workflow and configure webhooks instead which means we have to create a new integration API (with auth) to catch the hook requests, which then has to implement it's own queues and services. See what I mean? If you still think stand alone is the way to go, I'm all ears just wanted to offer a little more context and see if this changes anything. Commented Sep 12, 2018 at 2:24
  • 1
    Hmm, I see what you mean. I don't thinks it's particularly hacky to consume your own webhooks, but I guess in my opinion it comes down to whether you're looking to replicate or expose the functionality in the future - if not, the additional abstraction layer may not be worth it. Commented Sep 12, 2018 at 4:02
  • You also need to consider which team is building what and how is this new functionality is going to be used in the future. Commented Sep 12, 2018 at 12:16