gregjohnson

gregjohnson

Hi, the " Dispatch returning aggregate version" section of Commanded docs includes:

“You can optionally choose to include the aggregate’s version as part of the dispatch result …
This is useful when you need to wait for an event handler … to be up-to-date before continuing execution or querying its data.”

Does anyone have any hints as to the best way to use the aggregate version as a method for waiting for an event handler to be up-to-date? (and/or any use case comparisons with using consistency :strong)

Thanks …

Showing Posts 1 to 4

drteeth

drteeth

Hello @gregjohnson,

Come join us on the Elixir Slack: https://elixir-lang.slack.com/ in the commanded channel if you are looking for more timely help. There are a number of us there.

If you are wanting to wait for an event handler to catch up to a particular event, one way to do it would be to publish an event over PubSub and wait for that event before moving on.

As an example, say you want to dispatch an OrderWidget command and wait for your OrderHandler to project an OrderSummary record for a corresponding WidgetOrdered event. For the example the order is received via a REST API controller:

defmodule Foo.OrderController do
  def create(conn, order_params) do
    # listen for all order summary events
    Phoenix.PubSub.subscribe(Foo.PubSub, "order_summaries")

    # dispatch the command
    {:ok, %{aggregate_version: version}} =
      Foo.CommandedApp.dispatch(command, include_execution_result: true)

    # wait for the handler to process up to the event
    receive do
      {:order_summarized, v} when v >= version ->
        # the handler has run at least as far as we want
        # query for the summary and return a result
    after
      5000 ->
        # we've waited long enough
        # tell the caller that we accepted their order, but
        # we're having trouble... =(
    end 

    # we're done listening for events
    Phoenix.PubSub.unsubscribe(Foo.PubSub, "order_summaries")
  end
end

The handler might look something like:

defmodule Foo.OrderHandler
  use Commanded.Event.Handler,
    application: Foo.CommandedApp,
    name: "OrderHandler"

  def handle(%WidgetOrdered{} = event, metadata) do
    # write the OrderSummary record to the database
    summary = ...

    # broadcast over pubsub that we've handled this event
    Phoenix.PubSub.broadcast(Foo.PubSub, "order_summaries", {:order_summarized, metadata.stream_version})

    :ok
  end

You could use strong consistency as mentioned in the docks, but that try to avoid that where possible.

Finally, you might also try to get away with returning the input params as result: if you have successfully dispatched the command, then we know the input params were good:

defmodule Foo.AddressController do
  def update(conn, %{"id" => id, "street" => street, "city" => city}) do
    command = %ChangeAddress{address_id: id, street: street, city: city}
   :ok = Foo.CommandedApp.dispatch(command)

   # we know street and city have been accepted, so we can safely return them
   json(conn, %{address_id: id, street: street, city: city})
 end
end
gregjohnson

gregjohnson OP

Hi @drteeth,

Thanks for your commanded channel invite! … I’ll do that!

Just for completeness if anyone else comes here …

Thank for your comprehensive reply, yes, I’m familiar with the various strategies for ensuring that consistency has caught up.

Given that the commanded docs say:
“You can optionally choose to include the aggregate’s version as part of the dispatch result … This is useful when you need to wait for an event handler … ",

… my question was specifically as to how one might best use the dispatch returned aggregate version to wait for an event handler and/or any use case comparisons with the more well known strategies such as you gave in your reply.

Thanks again @drteeth …

drteeth

drteeth

@gregjohnson let’s chat in Slack. I’m not understanding what you are looking for, I thought that is what I showed.

gregjohnson

gregjohnson OP

@drteeth, my sincere apologies, I misread your reply. You did indeed completely answer my question. I really appreciate the time you took to provide such a comprehensive answer in the first place and I’m really sorry for wasting your time caused by my lack of proper attention to your initial reply. I’m very chastened … I’ll do better in the future …

Thanks again for referencing the slack commanded which has a lot of good stuff from people with real world implementation issues and I’ll head there in the future.

Regards …

— All posts loaded —

Where Next? Top

Trending in Questions Top

Hellowman
Hello everyone! I am new to coding with Elixir/Erlang. And i am looking for some utilities for fuzzing testing like AFL++. Does anyone ...
New
yarrichar
I’m very new to Elixir, so sorry if this is a silly question: I am wondering what happens to the mailbox of a process when the machine i...
New
pragdave
How do I tell Hologram not to escape HTML when substituting into templates? {Textile.render(@product.long_description)} escapes the HTM...
New
Fl4m3Ph03n1x
Background When trying to execute mix release on a Windows 11 machine for a Phoenix project I get the following error: * assembling mark...
New
mandar1045
I load tested a plain Phoenix chat app backed by Postgres with 100 million messages in it, everything on default settings, to see what br...
New
rlipscombe
I’d like to create a file with 600 permissions (rw-------), but there’s a race condition if I create it and then change the permissions. ...
New
saleyn
Is there a way to import record definitions in the iex shell for pretty printing (similar to the rr command in the erl shell)? This woul...
New

Other Trending Topics Top

dominicletz
Hey there, I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first. ...
New
raa-ziq
Hi everyone :waving_hand: I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
mudasobwa
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
OndrejValenta
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly) AI dream has many faces, but general...
New
kip
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
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