YSS
Hello, we are running an API with Elixir/Phoenix and when we push a new version, the server goes down for a small amount of time and this is causing issues for our API users.
I have looked into the Hot Code Loading, but wanted to ask people here what their opinion is. Now we are running 1 server instance and we think blue/green deployments would be a solution to have 2 elixir/phoenix servers but we are then into the overhead of making sure the sessions are sticky and basically need to re-organize our complete application.
Thanks for any help if you encountered this situation.
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Bringing learning, work and compliance together since 1987.
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
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
**Building the future of software with AI, trust, and human connection.**
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 7- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
garrison
I’ve been happy using Caddy’s
reverse_proxywith Phoenix with very little configuration. I haven’t done blue/green with it but it seems like the cookie lb_policy would work for sticky sessions, though I guess not for API clients.But do you actually need sessions to stick? If you’re bringing up a new server don’t you actually want new connections to go to the new server?
rhcarvalho
What’s your current infrastructure like? Deployment strategy and tooling?
hauleth
You do not need hot code reload, you need better deployment strategy and connection draining (so requests “in progress” will be finished).
There are different options how to achieve seamless deployment and from my experience - if you can avoid hot code reload, then it is better to avoid it.
YSS
github acdtions → deploys to single instance elixir/phoenix server
i can setup 2 elixir servers but how will the session sharing work with elixir phoenix if i don’t use sticky sessions? do you have expeirence with this?
YSS
the sessions draining in blue/green deployment isn’t an issue
it’s also the exlir/phoenix webinterface app that will need sticky sessions or i will have to store the sessions if they are shared
LostKobrakai
By default sessions are cookie based. The only shared knowledge the servers need is the secret_key configured on the endpoint. Everything is sent to the client and back. That’s at least the case unless you switched to a different session implementation.
YSS
ok thanks so auth on server1→ cookie session is set on client, we use server2 all of a sudden but we sill use that same session and it’s accepted by server1 and server2 because they use the same secret_key?
i remember my elixir phoenix app locking the postgres, how does this work wihen 2 servers connect to the same postgres? arent they both try to lock the tables they work with? thanks!!