antonmi
Dear alchemists!
I wanna start a topic about Flowex library here!
Flowex is a Flow-Based Programming framework for Elixir.
If you have never heard about the library I would recommend you read the library Readme and this post on Medium.
If you are familiar with Flowex check the latest version, the library has been improved significantly since the first release.
Recently I’ve published post Flow-Based REST API with Flowex and Plug which has an example of designing approach with FBP paradigm and benchmarks that shed some light on Elixir GenStage performance.
So, check it out, share your thoughts and ask questions.
Trending in Announcing
Flop is an Elixir library that applies filtering, ordering and pagination parameters to your Ecto queries.
offset-based pagination with...
New
I needed to reuse React components from my Chrome extension in my Phoenix/LiveView backend. I noticed that for Svelte/Vue, there are live...
New
I released Doggo, a collection of unstyled Phoenix components.
https://github.com/woylie/doggo
Features
Unstyled Phoenix components....
New
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hello
Published a new library - ProcessHub!
ProcessHub is a library designed to manage process distribution within the Elixir cluster. ...
New
I’ve started working on a new library to run SQL queries and do basic business intelligence.
Think “Blazer for Elixir.”
Currently it fe...
New
Other Trending Topics
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
This showed up on my feed.. anyone heard of it? Just hype?
Ox Alpha is a reasoning model designed for coding, sustained ag...
New
Hey folks,
I just published a post about Hologram’s funding and where the project goes next - the short version:
Curiosum as Main Spons...
New
:microphone: ElixirConf 2026 - Call for Talks is open!
We’re heading to Chicago :united_states:
:round_pushpin: In person + virtual
:d...
New
What IDE or editor are you using for Elixir development?
Personally, I use Zed, and I really like it, but sometimes I wish there were a ...
New
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
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex










Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
OvermindDL1
I’m curious, if there can only be one
error_pipe :error_handlerand its order does not matter, why not add it as an option touse Flowex.Pipelinelikeuse Flowex.Pipeline error_pipe: :error_handleror even as a full argument to make it more explicit?Cool design overall!
antonmi
Hi @OvermindDL1
“Physically” error_pipe is always the last pipe in a pipeline. And components are ordered in the way you define them, so it is natural to place error_pipe after all defined pipes.
OvermindDL1
True, but conceptually it is a side path that everything takes another path to if they error, but is skipped if not.
ikim
Hi, Anton,
I am new to Elixir and Flowex. I am trying to find a usage of Flowex for a project, but I have a question.
I created a pipeline as below.
Also, as you guided, I connect the pipeline to superviser (strategy: :one_for_one).
The pipeline is up and running OK. For curious, I killed the pipeline process, but I can see only Producer process is back, but not the others. Is it what you expected or do I miss any?
Below screen shots are before and after killing the pipeline from :observer.
Red lined Flows are what I created and the other processes are created by Flowex pipeline.
Before
Thank you for advance.
KIM.
ikim
Since I am a new user, I can post only one image. So below is after screen shot.
After

antonmi
Hi @ikim
Seems like you kill the supervisor of the pipeline. This is very unexpected case. Current implemetation start supervisor with producer only and then adds stages one by one and subscribe to each other. So it will fail to restart all the stages after supervisor crash.
But I think this can be changed. May I ask you to create an issue with the example?
Thanks!
ikim
Thank you @antonmi
I created an issue in the github.
antonmi
@ikim
I’ve changed starting strategy for pipeline.
Please, try the new 0.5.2 version of the library.
ikim
@antonmi
Yes, it works as I expected. I appreciate your quick help!!!
ikim.
antonmi
You are welcome!
Thank you for the issue which makes Flowex better!