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
Hey everyone!
Req is an HTTP client for Elixir that I’ve been working on for quite some time. There is already a lot of HTTP clients out...
New
Samly can be used to enable SAML 2.0 Single Sign On in a Plug/Phoenix application.
This library uses Erlang esaml to provide
plug enabl...
New
Flop is an Elixir library that applies filtering, ordering and pagination parameters to your Ecto queries.
offset-based pagination with...
New
The repo is at GitHub - cyberchitta/openai_ex: Community maintained Elixir library for OpenAI API · GitHub.
Docs are at OpenaiEx User Gu...
New
The Chelekom project is a library of Phoenix and LiveView components generated via Mix tasks to fit developer needs seamlessly.
One of i...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Hi all!
I want to present a small library which provides a mix task for generating an Entity-Relationship Diagram for Ecto schemas.
You...
New
Other Trending Topics
I am seeing a lot of aplications of Argumentum ad Vericundiam in software discussions. They do link some piece of writing and point us to...
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
Fly’s CEO posted this recently - Turn And Face The Strange · The Fly Blog
It says that Fly is going all-in on sprites, which is a worry ...
New
We’re evaluating API mocking tools for OpenAPI-based projects and would love to hear what other teams are using.
We’re particularly inte...
New
Today we’re releasing Oban for Python. Not an Oban client in Python. Not a pythonx wrapper embedded in Elixir. Nope, it’s a fully operati...
New
I was thinking since Goatmire Elixir turned out pretty good I should maybe do another one. 30th of Sep - 2nd of Oct this year./
The firs...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #elixirconf-us
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










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!