jpbecotte
I’ve been using Elixir and Phoenix for two projects, yet. I like Phoenix, but having in mind that server-side templates is nowadays less sexy (I am in love with Vue.js), what would be a great match for a new project which have the following requirements:
- Must use Websockets for communication between front-end and back-end, regardless of the realtime features. No REST API. HTTP(S) is used only to serve static content and for authentication.
- Backend must handle PubSub (like Channels in Phoenix).
- Data model with Ecto/PGSQL
I think Phoenix still a great match, but isn’t an overkill?
Thanks,
JP
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
yurko
The nice thing about Phoenix is that that it doesn’t have much overhead
So my two cents - definitely Phoenix, it’s WS support is really awesome.
chrismccord
Nope, not overkill
Since you need distributed PubSub you’ll find it a fantastic fit. Also since you want Ecto, you’ll find integration of protocols thru the
phoenix_ectoproject that makes your life easier.Lastly, the inclusion of server-side templates does not make it overkill, after all
Phoenix.Templateamounts to only 400 LOC:https://github.com/phoenixframework/phoenix/blob/master/lib/phoenix/template.ex and the majority of folks need to render an index page at any rate
brightball
I was basically coming here to say what @yurko said. People tend to assume that Phoenix is heavy, but it’s really just a thin layer around Plug. You’re not looking at a difference of raw ruby vs rails or something along those lines.
It’s one of the things that makes it such an easy go-to for…everything.