ion

ion

After reading the documentation on Contexts, I’m wondering how to best structure contexts for a realtime weather app that broadcasts temperature readings via channels from either Agent or GenServer (streaming CSV or JSON files), or using Postgres LISTEN/NOTIFY.

Any feedback is highly appreciated!

city.ex

schema "city" do
field :city_name, :string
has_many :temp, App.Temperature
has_many :precipitation, App.Temperature
end

temperature.ex

schema "temperature" do
field :temp, :float
field :precipitation, :float
belongs_to :city, App.City
end

-lib
my_app
city
---- city.ex
---- temperature.ex
my_app_web
channels
---- temperature_socket.ex

Showing Posts 1 to 3

kelvinst

kelvinst

One important thing to notice: it’s better to use contexts to separate concerns on your system and not just grouping schemas by itself. So I would do something like:

  • lib
    • my_app/weather
      • city.ex
      • temperature.ex
    • my_app_web/channels
      • temperature_channels.ex

Maybe, once your system grows with more and more schemas, you could separate the city on another context called “locations” or something like that, but I would not do that on the beginning because it would just make your system more complex needlessly.

ion

ion OP

Thank you for your input.

In your example, “weather” is the context and city and temperature are the schemas?

Do you think it’s a good idea to then have the following setup? My concern is with channels. Specifically, I want to broadcast temperature updates in real time but separating each city to its own lobby/room so I can broadcast updates for each city individually. I don’t know if it’s better to create a JSON api that will trigger (e.g when there’s a new temperature update) a broadcast event for the channel, or to rely on Postgres listen/notify feature (hence the brief excerpt of the simple associations below)

2 tables:
city (parent) and temperature (child)

City has many temperatures.
Temperature belongs to City.

city_id is the foreign key in Temperature.

kelvinst

kelvinst

Correct.

Well, I would do this:

  • lib
    • my_app/weather
      • city.ex # schema
      • temperature.ex # schema
      • weather.ex # context
    • my_app_web/channels
      • user_socket.ex # socket
      • city_channel.ex # channel

Then in my_app_web/channels/user_socket.ex:

defmodule MyAppWeb.UserSocket do
  use Phoenix.Socket

  ## Channels
  channel "city:*", MyAppWeb.CityChannel

  # ...
end

And in my_app_web/channels/city_channel.ex:

defmodule MyAppWeb.DashboardChannel do
  use MyAppWeb, :channel

  alias MyApp.Weather

  def join("city:" <> id, _payload, socket) do
    {:ok, Socket.assign(socket, :city_id, id)}
  end

  def handle_in("update_temperature", params, socket) do
    case Weather.update_temperature(socket.assigns[:city_id], params) do
      {:ok, temperature} -> broadcast! socket, "update_temperature", %{body: temperature}
      {:error, cs} -> # handle your error
    end
    {:noreply, socket}
  end
end
— 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
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