sorentwo

sorentwo OP

Oban Core Team

I’ve posted a “recipe” on enforcing unique jobs with Oban. It is the first in a series of recipe posts, and was largely drawn from the discussion in this thread. (This is also linked in the monster “Blog Posts” thread)

Oban Recipes Part 1: Unique Jobs

8
Post #61
benwilson512

benwilson512

Author of Craft GraphQL APIs in Elixir with Absinthe

Thanks @sorentwo, been using Oban for a few weeks now, very happy with it. In the initial post you teased a UI for visualizing the workers and job queues, is there a timeline or roadmap with respect to that UI?

7
Post #62
wolfiton

wolfiton

@sorentwo,

Would you be interested in vue implementation of the ui with some filtering using absinthe?

0
Post #64
sorentwo

sorentwo OP

Oban Core Team

Personally, no, I’m trying to avoid heavy JS where possible.

The current live view powered UI works wonderfully and I’m really pleased to be writing Elixir for everything. The remaining blockers are:

  1. Some ugly bugs (literally)
  2. A few missing core features
  3. Install and usage documentation
  4. The dependency on phoenix_live_view means I can’t release it on Hex
8
Post #65
wolfiton

wolfiton

So you need someone to write docs and create a tutorial on how to use your package?

0
Post #66
wolfiton

wolfiton

Also can oban be used for email marketing self solution as a newsletter sender?

Thanks in advanced

0
Post #67
sorentwo

sorentwo OP

Oban Core Team

Not exactly. The writing effort is around integration, a changelog, subtleties of behavior, and establishing a roadmap. The process of explaining those things to somebody (or multiple somebodies) would be equivalent to writing the docs :slightly_smiling_face:

Certainly. It’s up to you how you make use of it!

2
Post #68
wolfiton

wolfiton

I need check it later after you create the docs.

T

Thanks

0
Post #69
dch

dch

awesome! Is there (in the code) a pretty hard dependency on PG? I have a use case for a similar front end but with a distributed DB, I’d be interested in extending it at some point.

1
Post #70
sorentwo

sorentwo OP

Oban Core Team

Yes, there are a number of hard dependencies on PG features. A few off the top of my head:

  1. Pub sub through pg_notify
  2. Software advisory locks
  3. Use of SKIP LOCKED
  4. Partial indexes

There are probably others that I’m missing, but those are fundamental enough to how Oban operates that I can’t foresee porting it.

Dropping Ecto as a requirement or writing a port in another language is more likely that working with a different database.

2
Post #71