Introducing webhookie!

What a massive milestone! 10 months ago webhookie was just an idea and now through the help of an awesome team, the newly formed Hookie Solutions team, we are releasing our first version of the Community Edition of webhookie!

What is webhookie?

We hope it’s a product that changes how backend integration is done forever. No more complicated integration projects, no more unnecessary polling for updates. We want to bring the simplicity and beauty that REST APIs have brought to request/response user interaction integrations to the backend asynchronous event-driven integrations.

We, at the Hookie Solutions team, believe that all products being built today should offer at least two integration mechanisms:

  • Discoverable REST APIs to cover all your request-reply “frontend” integrations
  • Discoverable Webhook APIs to cover all the publish-subscribe “backend” integrations.

And this is where webhookie fits in! webhookie is a container-based product that adds enterprise-level webhook capability into any microservice or integration architecture. In fact, as long as your product can call an API you can use webhookie.

What do we mean by production-level webhook capability? Well we mean webhook capability that provides:

  • Webhook discoverability – allow your API consumers to easily discover your webhooks through a white label developer portal
  • Webhook management – allow your API providers to easily deploy and manage their webhook APIs
  • Subscription management – allow your consumers to manage their own subscriptions
  • Guaranteed delivery – make sure your consumers don’t miss a message
  • Traceability and transparency – allow your consumers to inspect the traffic being sent to their callbacks
  • Security – end to end security for your webhooks
  • Scalability – an architecture that scales to any load

And with the production-level webhook capability, we think we will have made the world of integration a better place.

The value of webhooks

Why do we love Webhook APIs so much? It’s not like we don’t love REST APIs, we love REST APIs, we really, really do! It’s just they don’t solve all your integration needs and we think webhook APIs are REST APIs perfect side-kick. APIs can get all the glory upfront (webhooks aren’t jealous) while webhooks can do all the dirty work at the back.

Let me explain… REST APIs are great for request/response interactions with your backend system – basically when we want to perform a CRUD function on an object. We call the REST API and get a response back directly saying that it was executed either successfully or not. So if your system manages Orders for example your system should have an Orders REST API so you can provide any type of experience you want to a user to manage and view those Orders. Sounds like the job is done. Why do we need webhooks?

Well, what about all of the other systems out there that might not manage Orders but want to know when new Orders are created? What about business partners who are part of the supply chain and need to get that Order? Well, this is where we think webhooks fit in nicely. Normally we solve these types of integrations with either an integration bus, EDI (for those partners), polling an API or as we see more and more some platforms and applications are providing webhook capability. All of these work but it’s a case of the good, the bad, and the ugly or more accurately, the expensive, the unintelligible, the inefficient, and the not quite there yet.

Integration buses are good, event-driven, reliable but they are also expensive and time-consuming and while we try to make nice generic integrations, they are not discoverable, and therefore re-use is often poor.

EDI, what can I say? It’s been around. It works but it is also expensive, partners can’t self onboard, they are not discoverable and many developers just don’t want to deal with it.

Checking if new orders have been created by polling a REST API? Well, we love our REST APIs so please don’t abuse them. We all know this is inefficient, doesn’t scale and we want to know when new Orders are created, not 30 seconds or 5 mins after they were created.. time is money people!

That leaves webhooks, event-driven, use JSON, HTTPS, all technologies that make integration easy. They are subscriber managed which is great, no one likes to be bothered about integrating. They just need to be souped up a bit. If we add discoverability, throw in a bit more security, guaranteed delivery, and traceability then in our opinion we have found a winner!

So coming back to what is webhookie? It’s souped-up Webhook capability, provided in a container by Hookie Solutions, that you can add to any product you’re building today and by adding it you’re going to make your product that much more valuable and useful to your customers!

Available to download.. for free

Yes, that’s right, we think production-grade webhook capability should be available to anyone to use for free – I did say we want to make the world of integration a better place!

So please give our Community Edition of webhookie a try and give us your feedback, we’d love to hear it!

And if you’re an enterprise looking for that bit extra, we’d love to hear from you too! Our webhookie enterprise edition will be releasing soon and with it, we are confident that it will meet your needs!

Webhookie is available on Docker Hub and the instructions to download the container are here at our website.

Look forward to hearing from you soon!

The Hookie Solutions Team!

1 comment

Leave a comment

Your email address will not be published.