svix-webhooks
Node RED
svix-webhooks | Node RED | |
---|---|---|
66 | 200 | |
2,088 | 18,596 | |
3.4% | 1.0% | |
9.6 | 9.3 | |
7 days ago | 7 days ago | |
Rust | JavaScript | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
svix-webhooks
-
Show HN: Hatchet – Open-source distributed task queue
That's exactly why we built Svix[1]. Building webhooks services, even with amazing tools like FastAPI, Celery and Redis is still a big pain. So we just built a product to solve it.
Hatchet looks cool nonetheless. Queues are a pain for many other use-cases too.
1: https://www.svix.com
-
Webhooks suck, but here are alternatives
Obviously Deno have vested interest it (and so do I as the founder of Svix[1]), but my take is that webhooks are great, though there are alternatives that could be better or complementary depending on the situation.
At Svix we also support running JS instead of sending webhooks (using Deno!), and it is very useful, but there are many limitations with this approach, and in general oftentimes people just want the data passed to their systems and deal with it there. Not write a bit of JS to do something ad-hoc.
So in short, like always with software engineering: "it depends" and there are tradeoffs to each approach.
1: https://www.svix.com
-
A list of SaaS, PaaS and IaaS offerings that have free tiers of interest to devops and infradev
Svix - Webhooks as a Service. Send up to 50,000 messages/month for free.
- Svix – Webhooks as a Service
-
Enhance Rust errors with file and line details
We opted for a more manual approach, we have a ctx!() macro[1] we use for wrapping errors we want to enrich thay we use like this[2]: ctx!(some_fallible_fund(foo))?
I wodner if anyone is doing anything better? The nice thing is that we have relevant fields in our error type, so we get a full backtrace out if it.
1: https://github.com/svix/svix-webhooks/blob/main/server/svix-...
2: https://github.com/svix/svix-webhooks/blob/main/server/svix-...
-
Ask HN: Standard for webhook source IP declaration?
This is what we do at Svix: https://docs.svix.com/receiving/source-ips
I've seen other companies (e.g. Stripe) also offer it via JSON, but I personally think it's not that important to provide it in a machine readable format if you don't plan on changing it; which you shouldn't as it'll break integrations. You should only add new IPs that can only be allocated to new customers.
P.S, if you'd like to start sending webhooks, you should probably check out Svix: https://www.svix.com
-
Looking for something that can create/manage webhooks
If I understand you, you just want some queue system, like kafka.But if you want a whole app who handle all your webhooks usage you can see : https://github.com/svix/svix-webhooks/
-
I need some explanation regarding webhooks?
Might want to look into Svix and HostedHooks
-
Official /r/rust "Who's Hiring" thread for job-seekers and job-offerers [Rust 1.69]
Repository on Github: https://github.com/svix/svix-webhooks
- Open source webhook service
Node RED
-
Devin, the First AI Software Engineer
Good question.
I expect that we're moving into a phase of AIs talking to AIs, and initially it'll be wasteful (because it'll be mostly English), but eventually, they'll derive their own language and seamlessly upgrade protocols when they determine they're talking to an AI. No clue how that will come about or what that language will look like, but honestly, it's kind of exciting.
Really interesting to think about how they might handle context, as well. Even though we have much bigger context windows (and they'll only get larger), context management is still a resource-management issue, which we'll probably continue to refine, as well. Imagine different strategies for managing both what is brought into the context of each request, as well as what form it could take (level of detail, additional references or commentary on it, etc). Things could get really unreadable even in English, and still be very interpretable for an LLM.
W.r.t. the graph-oriented interfaces, are you thinking something like Node-RED [1]? I'm seeing more and more people mention having LLMs produce non-text or structured outputs, like JSON, UI, and other things. Easy to imagine an LLM that wires together various open-source platforms, on-demand. Something like Node-RED for pipelines/functions, some UI tools for visualization/interactivity, other platforms for messaging, etc...
[1] https://nodered.org/
- IFTTT is killing its pay-what-you-want Legacy Pro plan
- Node-RED: Low-code programming for event-driven applications
-
Pipe Dreams: The life and times of Yahoo Pipes
I skipped to chapter 9 in the article ("Clogged"), and it looked like Pipes failed because it didn't have a large enough team or a well-defined mission. As a result they couldn't offer a super robust product that would lure in enterprise users. "You could not purchase some number of guaranteed-to-work Pipes calls per month" is the quote from the article.
The reason I think that interesting is because that's the model these days for everything from AI tokens to Monday.com seats. It makes me feel like Pipes was before its time.
That said I've been collecting different "business glue" products that are similar to Pipes. To me, like you say, they aren't as interesting, exciting and intuitive as Pipes was, but maybe it just takes a little more digging. I tried to focus on open source tools but some aren't.
- n8n io: https://n8n.io/integrations/mondaycom/
- Node-RED: https://nodered.org/ (just read about this one in this thread)
- trigger dev: trigger.dev
- automatisch.io: https://automatisch.io/docs/
- Activepieces: https://www.activepieces.com/docs/getting-started/introducti...
- Huginn: https://github.com/huginn/huginn
- budibase: https://budibase.com/
- windmill: https://www.windmill.dev/
- tooljet: https://www.tooljet.com/workflows
- Bracket: https://www.usebracket.com/pricing (just SalesForce <-> PostgreSQL)
- Zapier: zapier.com/
Anyway I hope some of these are fun!
- Open source IPaaS With Drag and Drop integration
- Ask YC: tracking events platform and no-code workflow
-
#OpenSourceDiscovery 84 - Node-RED, alternative to IFTTT or Zapier, a workflow automation tool
Source: https://github.com/node-red/node-red
- Low-code programming for event-driven applications
-
n8n.io - A powerful workflow automation tool
I believe Node-RED (https://nodered.org/) the way to go. It's just an NPM package to install and you can run it how ever you wish (even on Windows). It has a friendly and helpful community with even the main developers tirelessly answering even beginner level questions. In fact the community forum its THE friendliest forum I've ever been a member of by a large margin. Node-RED's development is supported by the JS Foundation and it's completely free and open source. It's widely used in the industrial automation industry and even integrated by some PLC manufacturers such as Siemens.
-
Loops and conditional branching (IF then else) in ComfyUI?
Does anyone know if their are plans to implement something like this (or if there are already custom nodes out there). I'd like to experiment with things like looping and incrementing values (like a for loop) for a Ksampler for example. It's only an example though, so I am not looking for a ksampler specific solution; just a generic way to have a variable (e.g. Seed value), run some nodes that use that value, increment the value, and then loop back to the beginning until some sort of condition is met. Node-Red (an event driven node based programming language) has this functionality so it could defintely work in a node based environment such as ComfyUI (see here).
What are some alternatives?
convoy - The Cloud Native Webhooks Gateway
Home Assistant - :house_with_garden: Open source home automation that puts local control and privacy first.
pg-boss - Queueing jobs in Node.js using PostgreSQL like a boss
n8n - Free and source-available fair-code licensed workflow automation tool. Easily automate tasks across different services.
hookdeck-cli - Receive events (e.g. webhooks) in your development environment
openHAB - Add-ons for openHAB 1.x
python-ksuid - A pure-Python KSUID implementation
Huginn - Create agents that monitor and act on your behalf. Your agents are standing by!
fib - Performance Benchmark of top Github languages
esphome - ESPHome is a system to control your ESP8266/ESP32 by simple yet powerful configuration files and control them remotely through Home Automation systems.
Programming-Language-Benchmarks - Yet another implementation of computer language benchmarks game
blockly - The web-based visual programming editor.