Add Phoenix: Elixir web framework on BEAM/Cowboy (first Elixir entry! ~23k ⭐)#70
Open
BennyFranciscus wants to merge 2 commits intoMDA2AV:mainfrom
Open
Add Phoenix: Elixir web framework on BEAM/Cowboy (first Elixir entry! ~23k ⭐)#70BennyFranciscus wants to merge 2 commits intoMDA2AV:mainfrom
BennyFranciscus wants to merge 2 commits intoMDA2AV:mainfrom
Conversation
Phoenix router doesn't auto-merge query params into controller params without either Plug.Parsers or explicit fetch_query_params plug.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phoenix — Elixir Web Framework on BEAM
Phoenix is THE Elixir web framework — ~23k GitHub stars, the most popular framework in the BEAM ecosystem. First Elixir entry in HttpArena.
Why this is interesting
HttpArena already has
gleam-mist(also BEAM) — Phoenix adds the framework that most BEAM developers actually use in production. Phoenix on Cowboy vs Gleam on Mist: same VM, different languages, different HTTP servers. Plus the comparison with traditional frameworks (Flask, Express, etc.) shows how BEAM's preemptive scheduling and lightweight processes handle concurrency differently from thread pools or async/await.Implementation
:persistent_term(global read-optimized BEAM storage)Tests enabled
baseline, noisy, pipelined, limited-conn, json, upload, compression, mixed
cc @chrismccord, @josevalim — would be cool to see how Phoenix stacks up in HttpArena! The gleam-mist entry is already there for a BEAM-vs-BEAM comparison.