kyde

kyde

I have a module where am using GenServer. In this module the state is a list of items. The module exposes functions to filter these items according to various criteria.
My question is what is the best approach to solving this task. Would it be better to:

  1. Add multiple handle_call callbacks for each filter criterion.
  2. Use the list_items functions and then filter its return value using multiple helper functions instead of the multiple handle_call callbacks.

Here is a simple implementation of the first approach:

defmodule Repositories do
  use GenServer
  
 ## API
  def start_link(_opts) do
    .GenServer.start_link(__MODULE__, :ok)
  end

  def list_items(pid) do
    GenServer.call(pid, :list_items)
  end

  def filter_by_name(pid, repo_name) do
   GenServer.call(pid, {:filter_by_name, repo_name})
  end
  
  # Other APIs here for filtering by other criteria
   ....

  ## Server
  def init(:ok) do
    initial_repos = #Fetch initial repos.
    {:ok, initial_repos}
  end

 def handle_call({:filter_by_name, repo_name}, _from, state) do
   matching_repos = Enum.filter(state, fn repo -> String.equivalent?(repo.name, repo_name) end)

   {:reply, matching_repos, state}
 end

  def handle_call(:list_items, _from, state) do
    {:reply, state, state}
  end

  # Other callbacks here for handling calls to filter by the other various criteria
   ....
end

Here is a simple implementation of the second approach:

defmodule Repositories do
  use GenServer
  
 ## API
  def start_link(_opts) do
    .GenServer.start_link(__MODULE__, :ok)
  end

  def list_items(pid) do
    GenServer.call(pid, :list_items)
  end

  def filter_by_name(pid, repo_name) do
   pid
   |> list_items()
   |> Enum.filter(fn repo -> has_name?(repo.name, repo_name) end)
  end
  
  # Other APIs here for filtering by other criteria
   ....

  ## Server
  def init(:ok) do
    initial_repos = #Fetch initial repos.
    {:ok, initial_repos}
  end

  def handle_call(:list_items, _from, state) do
    {:reply, state, state}
  end

  ## Helper functions
  def has_name?(actual_name, repo_name) do
    String.equivalent?(actual_name, repo_name)
  end
  # Other  helper functions to perform filtering by other criteria
   ....
end

Which approach is more favored in the elixir community?

First Post!

stefanchrobot

stefanchrobot

I think this is more about your requirements than the favoured approach.

In the first case, the filtering is happening in the GenServer’s process. In the second case, the filtering is done in the client process. In most of the cases, the second one is preferred. If you have just a few of the Repositiories processes, then definitely offloading the work to the clients is the way to go.

Most Liked

al2o3cr

al2o3cr

The data structure you return from handle_call is copied back to the calling process. If state is large, this will make the second approach significantly more expensive to execute.

A third approach worth considering: have one handle_call that accepts a filter function:

def filter_by_name(pid, repo_name) do
  list_items(pid, fn repo -> has_name?(repo.name, repo_name) end)
end

def list_items(pid, filter \\ fn x -> x end) do
  GenServer.call(pid, {:list_items, filter})
end

def handle_call({:list_items, filter}, from, state) do
  {:reply, Enum.filter(state, filter), state}
end

This avoids copying state to the calling process by instead bringing filter to the data.

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
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
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
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New

Other Trending Topics Top

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
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
webofbits
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself. My main conc...
#ai
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews