ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #elixir
Scaling State Distribution Phoenix Channels rely on a pub-sub mechanism to synchronize state across a cluster. While the BEAM handles concurrent TCP connections efficiently via Cowboy, the memory overhead associated with maintaining active process states increases as the number of concurrent subscribers grows. When scaling to thousands of concurrent users, t
Context Since Phoenix 1.6 replaced the webpack/Node.js asset build with esbuild (and 1.7 made Tailwind the default), the asset toolchain is now reproducible through Hex: the esbuild and tailwind packages download pinned binaries based on versions set in config/config.exs , and mix assets.setup / mix assets.deploy replace any npm step. That part of a repeatab
Our Elixir project commits a .tool-versions file (used via asdf/mise) and mix.lock so every developer and CI runner builds with the same toolchain and dependency set. The dependency side is settled: the lockfile pins exact Hex versions and checksums. The unresolved decision is how tightly to pin Erlang/OTP relative to Elixir. Each Elixir release supports a d
Ecto + PostgreSQL: Schema Drift Detection After Restore When a PostgreSQL database is restored from a pg_dump archive, the application’s Ecto schema modules may no longer match the on‑disk structure. The migrations table can become out of sync if the backup predates recent migrations, leading to runtime errors or data inconsistencies. Currently, Ecto offers
Phoenix Channels leverage the Cowboy web server to maintain persistent WebSocket connections, utilizing the BEAM process model to isolate each client. In environments targeting millions of concurrent idle connections, there is a design trade-off between the memory footprint of maintaining these long-lived processes and the CPU/network overhead of aggressive
Goal: Assess whether Ecto can guarantee that a migration’s down function restores the database to its pre‑migration state after a schema change Ecto runs each migration inside a single transaction, but the generated down callback does not automatically undo data modifications that occur before the schema alteration. Certain schema operations—such as changing
Managing database connection pools in Elixir via Ecto and DBConnection requires balancing application responsiveness against database server resource limits. When a system experiences sudden, short-lived concurrency spikes, the pool can become exhausted, leaving processes to wait in the queue. One approach is to increase the pool_size to accommodate peak loa
When building an Elixir release with mix release , the values in config.exs are baked into the generated sys.config file. At runtime, any configuration key can still be overridden by an environment variable accessed via System.get_env/2 . This overlap makes it difficult to guarantee that certain keys remain immutable after the release is created. The goal is
When processing form data or API requests, Ecto.Changeset.cast/4 allows developers to convert empty strings to nil using the empty_strings_to_nil option. This prevents blank strings from being persisted in database columns where NULL is the preferred representation of missing data. Currently, this behavior is typically managed on a per-changeset basis. In la
phoenix
ecto