pedroassumpcao
Hi, I have a scenario with the following components:
Controller (a Phoenix one) → API (GenServer) → EventBus (GenEvent) → Worker (GenServer)
The applications are under an umbrella with the web layer, API and Messaging+Worker. For the web layer standpoint, I need to make sure of 2 things:
- API got my request
- job was done
But also for the web layer standpoint, the communication happens with the API only, how the API makes its work, it is an API concern.
One of my initial thoughts was having my API handle_call notifying the Messaging and listen to a message back, to then send the reply to the web layer. But I heard/read that is not good add a receive to listen general messages inside GenServer callbacks.
Other option is handling the worker messages in the API with handle_info, and send a message to the controller, but that will require having a receive to get the message in the controller side, what I don’t know if it is a good approach.
Any suggestions or comments?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Master modern tools, write cleaner code, and tackle real-world challenges with Manning books, videos, and courses. Start building today.
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
- #hex
- #security
- #metaprogramming
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.
Master modern tools, write cleaner code, and tackle real-world challenges.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
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 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Azolo
Why not? I mean, it could be a code smell in some situations, but every time you do a
GenServer.callyou drop into areceiveblock to listen for the response.BUT, you could just not reply in the
API.handle_callcallback and have yourWorkerreply using theGenServer.replyfunction. It wouldn’t block your APIGenServerwaiting for a response, and still allows for a timeout using theGenServer.callsemantics.pedroassumpcao
Thanks, I think I will return the
handle_callwith{:noreply, new_state}and insidehandle_infouseGenServer.reply/2.