Hacker News Reader

Comment by dgellow | Hacker News Reader

You can run trigger in your own infra. That has very little to do with the libraries used for your web app

Trigger and friends exist precisely because Node is not a serious backend runtime so you have to reach for bolt-ons for every little thing. No matter if trigger is open source or managed, it's an anti-pattern. Erlang/Elixir, C#, Go etc all handle this sort of async natively, literally out of the box. Mature frameworks like Rails, Django have pretty easy to use officially libraries as well. This has been a solved problem for literally decades.

That has nothing to do with node. You have a lot of situations where a dedicated job queue makes sense

The reason people are using these paid queue services is because Node sucks. Isn't it better to use an open source library or adult backend stack which solved this problem 30 years ago?

Trigger is literally open source. That has nothing to do with how mature the node ecosystem is. If you want in-process queue systems you have a lots of other mature options. Trigger is a dedicated queue system, it runs in its own process and can be used from any language through its API. You seem to talk confidently about a topic I don’t think you understand.

Go has lots of mature in-process queue systems, yet River exists, because in lots of situation it makes perfect sense to have your job queue in its own process

Yeah, I understand this topic really well, actually: https://github.com/agoodway/pgflow

Have you actually tried using the open-source self hostable version of trigger? It seems to only exist in order to check a "we're open source yay" box.

It's missing lots of features like sleeping on waits, warm starts etc.

Reply on news.ycombinator.com