Qqwy
How to optimize Phoenix for a channel-only application?
Hey everyone!
Some of you might know that we are working on a chat application. (The initial beta version will soon be released! Wooh!)
How it has been set up, is that the main chat server only has as goal to communicate with clients running in the user’s browser. This chat server itself does not do any HTML rendering (the front-end rendering code is on other people’s servers), and so will, besides sending one or two static JS files, only communicate using Phoenix Channels.
So I was wondering: Are there parts of Phoenix that can be turned off, or configured in such a way that it works extra well for channel-based communication?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Deploy Phoenix to your own VPS with PaaS ease: push-to-deploy, zero downtime, auto SSL, managed Postgres. 14-day free trial at potions.io
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #performance
- #security
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.
Practical resources that improve the lives of professional developers.
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!"
First Post!
sribe
Bah, I wrote the below thinking you were only using websockets–obviously you can’t drop Phoenix altogether and still use Phoenix Channels.
You could probably just drop Phoenix altogether and use Plug. I personally wouldn’t, because somewhere down the line you’re going to discover that in fact you don’t want a pure channels application. You’re going to want to respond to some plain HTTP requests: /healthcheck, /ready, /ping, etc. You might even want to serve some HTML: /admin/…
Most Liked
chrismccord
Nope
Channel transport connections are intercepted at the top of the endpoint, thus bypassing your plug pipeline, so there’s nothing to optimize. Even if you later decide to serve up other http requests, there won’t be a concern for such features impacting your channel performance.
Qqwy
I just want to say: What an amazing piece of engineering have you built, Chris!