4 ms·
> no way anyone is beating a Rails dev in setting one up I disagree. Elixir/Phoenix is as simple as Ruby/Rails and an order of magnitude more performant out of
by cpursley 8y ago
> no way anyone is beating a Rails dev in setting one up
I disagree. Elixir/Phoenix is as simple as Ruby/Rails and an order of magnitude more performant out of the box. Especially if you already know Ruby and the basics of functional programming. Plus, unlike Rails, you probably won't need separate servers for background jobs, websockets and caching.
- rishav_sharan 8y agoAnd if the next order of magnitude of performance is needed, there's always Crystal
- blunte 8y agoBut since it is much newer, the docs and examples are much thinner than Phoenix. Plus, except for unoptimized database actions (which would equally affect Crystal), Phoenix responses are usually sub 200ms. Some are sub 1ms. So it really isn't in need of performance increase. Ecto, however, is really not pleasant imo.
- trcollinson 8y agoSorry to fact check here but on my Rails app I am getting 200ms return times. This is running a web application and a few hybrid mobile applications. Are you saying that basically out of the box with Elixir/Phoenix I would get 20ms return times? That would be amazing but I find that highly unlikely.
- cpursley 8y agoYes, and likely faster. http://www.akitaonrails.com/2015/10/27/how-fast-is-elixir-phoenix http://www.akitaonrails.com/2015/10/27/how-fast-is-elixir-ph...
- trcollinson 8y agoThat’s quite interesting. I’m going to have to give this a try under real world condition. This gives a pretty good argument for massive improvement.
- regulation_d 8y agoFor my load balancer heartbeat checks, I'm returning responses in 200µs.
- trcollinson 8y agoThat’s a highly unrealistic real world scenario. I’d like to see a page under load with actual queries. Heartbeat checks are far from actual real world examples of much of anything.
- regulation_d 8y agoI guess my point was: that’s the baseline. It’s an order of magnitude faster the 20ms your saying is unlikely. That leaves a lot of headroom for hitting the db and things done. The api I’m working on isn’t currently being hit super hard, but for most of my endpoints 25ms is pretty average.