4 ms·
You already answered your question. 1. You spent hours building a small Go tool, assuming your hour is worth at least a $100 (certainly more) and say you spent
by dubcanada 5y ago
You already answered your question.
1. You spent hours building a small Go tool, assuming your hour is worth at least a $100 (certainly more) and say you spent 5 hours, that's $500.
2. You deployed it on a VM, that's $5 a month
3. You need to keep it updated and manage it, so let's say you spend 1 hour a month. That's a $100 a month.
So right now you spent $500 upfront, and $105 a month to keep it going, and that's assuming 1 hour a month which is crazy low.
You can replace that entire cost with a static Y x 0.001 + what ever up front cost to convert the system to use Svix, which can be factored into the system cost. I have 50,000 users, each user has 1 webhook I need 50,000 x average number of messages a month. Just add that on top of the system monthly cost.
It's a lot easier to manage from a business/accounting point of view a SAAS then your own homebrew.
- pm90 5y ago> It's a lot easier to manage from a business/accounting point of view a SAAS then your own homebrew. Hmm I would have to disagree here. This is something that most platform teams could build, deploy and forget about. Setting up an account, getting procurement to pay for it, not being able to see why it’s down etc just seems like a lot more hassle.
- onlyrealcuzzo 5y agoSo instead you should spend 5 hours reading about some service that might not exist in a year and doing integration work with it? It's not like you're going to integrate some service into your app in 0 hours. It's also not like you won't have to spend some time maintaining your integration either. IMO, a "killer feature" for a business is not /maybe/ saving $100 a month under low usage, and /maybe/ costing you $1k+ under high usage...
- edoceo 5y agoRight! Vendor driven churn is a costly burden. I'm going to post more about the tool later.
- tasn 5y agoFive hours is a gross underestimate for the time it takes to build a robust and scalable webhooks delivery system, and even that is just for the delivery system itself. You also need to build the UI for your users, libraries for verifying signatures and etc. All of this assumes you know what you are doing and can just write the code. It doesn't even take into account the research you need to do to make sure you cover all of the security (and other) consideration that GP seemed to have already known about and took care of.