axelson

axelson

Scenic Core Team

I am working with an external API (external from the Elixir server at least) and I want to minimize the amount of API calls to a particular endpoint. It feels like GenStage is a good fit for this use case but I’ve had a little trouble getting everything to line up.

I want to:

  • Collect all events every 100ms
  • Batch the events into batches of up to 150
  • Have three workers running in parallel to send these batched requests to the remote API

These seem to fit into three GenStage stages

  • Collector - GenStage :producer that collects events from other parts of the elixir system in a FIFO queue (based on :queue) and sends the events only in handle_demand/2
  • Batcher - GenStage :producer_consumer that asks the Collector for 1000 events every 100ms and batches them into batches of 150 (runs in :manual mode)
  • RequestSupervisor - GenStage ConsumerSupervisor that requests the batched events from the Batcher and starts workers that call the external API

The code I have seems to work but I feel like I may be going against the ethos of GenStage since I’m not really propagating demand all the way up the chain. Specifically the Batcher and the Collector both mostly ignore demand. The Batcher is set to :manual mode and asks for a static 1000 events every 100ms.

Another issue is that this setup will always incur a penalty of 100ms on each event even if there are more than 150 events that are added to the Collector at once.

But also keep in mind that I only expect about 5-10 events every 100ms (and maybe even less). But I want to have a good base for future scaling if necessary.

Any thoughts on this architecture? Is there anything that I haven’t considered that I should consider?

Showing Posts 1 to 2

axelson

axelson OP

Scenic Core Team

Or perhaps this setup would be better:

  • Collector - GenStage :producer that collects events from other parts of the elixir system in a FIFO queue (based on :queue).
    • When it receives events and has more than 150 events, then immediately emit the events.
    • Emit any full and partial batches of events in handle_demand/2
  • Delayer - GenStage :producer_consumer that asks the Collector for 1000 events every 100ms
    • Does this still need to run in :manual mode?
  • RequestSupervisor - GenStage ConsumerSupervisor that requests the batched events from the Delayer and starts workers that call the external API

I could probably find a better name than Delayer. Does this setup seem better? I think it might be because previously Batcher and Collector both needed to work together for Batcher to be able to actually batch events. Now batching events is the responsibility of the Collector. Also the demand can handled a little better in the Collector rather than just ignored, but now I need to prototype to make sure that I can get the batching to still work the way I want.

stefanchrobot

stefanchrobot

How about just using a plain GenServer with a FIFO queue and a timer?

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
apz
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New

Other Trending Topics Top

GenericJam
Edit: 2026 May 15 - This post is archived. Mob is alive!! Main docs: mob v0.7.11 — Documentation A bit of explanation for the slightly c...
New
JesseHerrick
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
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
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
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews