4 ms·
the solution is good but what tends to happen is webhook providers are not gonna work on such a solution - why - because it puts 'work' on them. hell this is w
by dzonga 2mo ago
the solution is good but what tends to happen is webhook providers are not gonna work on such a solution - why - because it puts 'work' on them.
hell this is without the proposal for a new protocol - just a 'GET' stream or paginated one like the author said.
whereas with web hooks - a consumer has to do all the work - as the article above outlined.
- weli 2mo agoDoesn't webhooks put even more work on them? You need to create a webhook dashboard, sometimes with multiple environments and administration endpoints, a way to set HMAC secrets, retriability and deliverability mechanisms, a local tunnel CLI for development, etc. With scroll if you already own a event log system the only work you need to do is exposing it to the client securely, same API keys as the rest of your existing REST api's.
- RyoSaeba89 2mo ago[flagged]