News for hackers. Stuff that matters.

darwin67

it depends on your load really. there are background job frameworks in other languages like Oban in Elixir that utilizes postgres.

if scale is low, it's not an issue. but once you have high usage, what typically people do is they move it to a separate database, otherwise you're saturating the resources and it starts impacting the application itself.

at that point, that's not much different from external state stored else where.

also another thing about databases is their ACID transactions can only handle up to certain amount of load. again, if you don't hit that limit, it's totally fine. once you do, which usually means outages, severe delays, etc, and it'll be a shit show.

disclaimer: I do work at Inngest, but also this is speaking from experience. :)

Re:Queues Aren't the Right Abstraction on Thursday March 28, 2024 @01:18PM (#39854605)
How are you going to do that over network boundaries? Especially the ones you might have less control over.
Re:Building a fair multi-tenant queuing system on Monday January 22, 2024 @03:49PM (#39095226)
Which part of BEAM are you talking about? I know some cases can be solved by it already, but not almost every need.

The fairness of the BEAM scheduler is not the same as multi-tenant fairness. I'm aware of lcnt in Erlang that helps with contention, but that will have a hit in throughput like any other locks.

Unless I'm missing something?

Re:Rethinking Serverless with Flame on Wednesday December 06, 2023 @12:04PM (#38546545)
FYI: there's an Elixir SDK for Inngest as well. Haven't fully announced it yet, but plan to post it in ElixirForum some time soon.

https://github.com/inngest/ex_inngest

Thanks for the note, it's changed to underscore now. Regarding the "ex" prefix, it's a common convention for Elixir libraries. https://github.com/h4cc/awesome-elixir
no promises here but I'd love to look into Rust in the future. there're essentially no background job systems for Rust iirc.