3 ms·
Just a small nit-pick here. If we're talking REST/graphql stateless APIs, sure the scalability gains may be a harder sell vs throwing hardware at the problem, b
by chrismccord 5y ago
Just a small nit-pick here. If we're talking REST/graphql stateless APIs, sure the scalability gains may be a harder sell vs throwing hardware at the problem, but the value-add depends on what's being built. I built Phoenix first and foremost for real-time, stateful web applications. So anything that requires websockets, frequent updates, PubSub, presence, etc, you will be extremely hard to match what our stack provides out of the box, performance wise, and distribution wise. Not everyone needs these things but increasingly companies do, ie chats, social feeds, dashboards, and now LiveView-like interactive applications all change the equation from "marginal" perf gains.
- ipnon 5y agoI am an Elixir evangelist, to be clear, but it's one thing to have believers and another to change the world. I think you are right that Phoenix will eventually win the day in regards to real-time, stateful Web applications. "Traditional" REST APIs may be a harder sell, and perhaps Elixir doesn't need to eat the entire Web to considered successful. There are still many Java developers at work after all. I am flattered to be critiqued by you!