Is Building a Message Queue System Using Pipedream Economical or Will It Consume Too Many Credits?

This topic was automatically generated from Slack. You can find the original thread here.

Does it make sense to build a message queue system using Pipedream like https://hookdeck.com/ ? Or will it eat up too much credits?

I think it’s really depend on your usecase and requirements. My recommendation is:
• assuming the usage of your usecase and do a rough estimation of cost for each platform. Each platform has their pricing page detailing their cost per event
• try implementing your usecase on both platforms to see their features and trade-off fit all of your needs. By this you will know for sure which one is the best for you. Maybe you might see it fit to use both of them together to leverage both of their strengths

Pipedream should work well as a message queue system. Credit usage and price would depend on your plan and feature usage. If your concern is mostly about price due to high volume, discounts are available for committed usage.

Noted, I could see how this could work with using the sources and workflow (for retry & recovery). Will try and see as we are trying to use it with a messaging system so the traffic could be high.

let me know how it goes and if I can be of help