fireproofsocks
I’m trying to wrap my head around some Oban workflows. You can group multiple jobs under a single workflow (I assume they share the same workflow ID). From the point of observability, is this any different than batching a group of jobs under a shared batch ID? From db queries, we can see which jobs were grouped together in either case… workflows allow us to specify dependencies… is there any other fundamental difference between workflows and batches? Is a workflow with no dependencies more or less the same as a batch? Is a batch basically a workflow with no special options?
Where Next?
Trending in Questions
Other Trending Topics
Latest Oban Threads
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
sorentwo
Workflows are about dependencies between jobs, like a directed graph. Batches are about events when job states change. The purpose of a batch isn’t just to group the jobs, but to have handler callback jobs when all jobs are
attempted,completed, etc.A workflow with no dependencies is less useful than a batch, because there aren’t any callbacks. Workflows are entirely meant for dependencies between jobs.
There’s an older, slightly outdated, Composing Jobs with Oban Pro article that outlines the differences. That article is becoming a guide in the upcoming Pro v1.5, and the differences should be much clearer.