sorentwo

7 ms·

31.
by sorentwo 1y ago
The architecture is remarkable. The lengths they’ve gone to for language version compatibility, and protecting app namespaces is especially impressive. https://github.com/elixir-lang/expert/blob/main/page
32.
by sorentwo 1y ago
Absolutely love monodraw for diagrams in documentation! All of the diagrams for Oban and Oban Pro are done this way: Job Lifecycle: https://hexdocs.pm/oban/job_lifecycle.html Composition: https://oban.pro&#x
33.
by sorentwo 1y ago
Oban doesn't use advisory locks for fetching jobs (unless there is uniqueness involved)—it uses `FOR UPDATE SKIP LOCKED` as well to pull jobs.
34.
by sorentwo 1y ago
The problem was with restrictive connections, not DNS based discovery for clustering. It wasn't possible (as far as I'm aware) to connect directly from one dyno to another through tcp/udp.
35.
by sorentwo 1y ago
Ping requires something persistent to check. That requires creating tuples, and most likely deleting them after they’ve been consumed. That puts pressure on the database and requires vacuuming in ways that pubsub doesn’t because it’s entire
36.
by sorentwo 1y ago
In app notifications, which can be disabled. Our triggers were only used to get subsecond job dispatching though.
37.
by sorentwo 1y ago
Very very few applications use mnsesia. There’s absolutely no way I would recommend it over Postgres.
38.
by sorentwo 1y ago
We have Postgres based pubsub, but encourage people to use a distributed Erlang based notifier instead whenever possible. Another important change was removing insert triggers, partially for the exact reasons mentioned in this post.
39.
by sorentwo 1y ago
Postgres LISTEN/NOTIFY was a consistent pain point for Oban (background job processing framework for Elixir) for a while. The payload size limitations and connection pooler issues alone would cause subtle breakage. It was particularly
40.
by sorentwo 1y ago
Shaun Ryder sets a low bar. Definitely the best maracas player though.
41.
by sorentwo 1y ago
That's the issue with goroutines, threads, or any long running chain of processes. The tasks must be broken up into atomic chunks, and the state has to be serialized in some way. That allows failures to be retried, errors to be examine
42.
by sorentwo 1y ago
Absolutely! Elixir's lightweight processes and distribution story make it ideal for orchestration, and that includes orchestrating LLMs. Shameless plug, but that's what many people have been using Oban Pro's Workflows for rec
43.
Elixir Outreach stipend for speakers and trainers(elixir-lang.org)
2 points by sorentwo 1y ago|0 comments
44.
Three Virtues(thethreevirtues.com)
4 points by sorentwo 1y ago|0 comments
45.
Elixir Performance Monitoring(honeybadger.io)
4 points by sorentwo 1y ago|0 comments
46.
Weaving Stories with Cascading Workflows(oban.pro)
1 points by sorentwo 1y ago|0 comments
47.
Weaving Stories with Cascading Workflows(oban.pro)
2 points by sorentwo 1y ago|0 comments
48.
Why hasn't commercial air travel gotten any faster since the 1960s? (2009)(engineering.mit.edu)
142 points by sorentwo 2y ago|667 comments
49.
Remote: Growing from Zero to Unicorn with Elixir(elixir-lang.org)
8 points by sorentwo 2y ago|0 comments
50.
Oban Web Is Open Source(oban.pro)
2 points by sorentwo 2y ago|0 comments
51.
by sorentwo 2y ago
Transparently parallel, lightweight tasks are part of the language in Elixir. Fully multithreaded and able to utilize all cores out of the box.
52.
by sorentwo 2y ago
What you’re describing sounds exactly like Elixir (any Erlang family language really, Elixir is just most ergonomic IMO). Truly seamless cooperative scheduling with transparent distribution between any number of nodes. Shameless plug, but t
53.
Relive the Biggest Little Runs in Paris(nytimes.com)
2 points by sorentwo 2y ago|1 comments
54.
Overhauled Composition–Oban Pro Launch Week(getoban.pro)
1 points by sorentwo 2y ago|0 comments
55.
Job Decorators–Oban Pro Launch Week(getoban.pro)
3 points by sorentwo 2y ago|0 comments
56.
Enhanced Unique and Distributed Postgres–Oban Pro Launch Week(getoban.pro)
2 points by sorentwo 2y ago|0 comments
57.
Unified Migrations and Job Chaining–Oban Pro Launch Week(getoban.pro)
1 points by sorentwo 2y ago|0 comments
58.
Princeton astrophysicists re-imagine world map (2021)(princeton.edu)
28 points by sorentwo 2y ago|12 comments
59.
Scaling a Streaming Service to Concurrent Viewers(elixir-lang.org)
5 points by sorentwo 3y ago|0 comments
60.
Optimizing Connections and Bloat in Oban Pro(getoban.pro)
1 points by sorentwo 3y ago|0 comments

More ›