12K views · May 24, 2016 · 28:34 · 4 HN recommenders · 7 mentions · discussed 2016
Brian Cardarella's RailsConf 2016 talk on why and how teams can move from Rails to Elixir and Phoenix. It covers performance gains without losing productivity and how to introduce Phoenix in an organization.
Why Hacker News points people here: HN points Rails developers to it as a real-world case for migrating to Phoenix, backed by numbers.
“A really great presentation, including numbers and real world backup data, plus conceptual overviews.”HN comment, 2016
“A really great presentation, including numbers and real world backup data, plus conceptual overviews.”
Great presentation with numbers, real-world data and conceptual overviews.
I'd say you really should have a look into this video . A really great presentation, including numbers and real world backup data, plus conceptual overviews.
“that may be a good start to empower you to make a decision”
Talk on switching from Rails to Phoenix.
I can't speak about experiences with Ruby/Rails since I don't use that stack but I can give you advice about both Scala and Elixir. I used to be a Java programmer and fell in love with Scala and functional programming. Scala helped me do things that I couldn't do so easily in Java in a more explicit way. However, I found doing web development with Scala to be more cumbersome than helpful but was still a great learning experience for FP in general. Since late 2015, I've been all-in on Elixir. Elixir does everything I wanted to Scala, specifically pattern matching everywhere and how powerful it is. Since Elixir uses BEAM, it's incredibly lightweight but can scale without any configuration. The community around Elixir is fantastic and helpful and everyone is growing together. Brian Cardarella (well known in the Elixir community) gave a conference talk at Rails Conf about switching from Rails to Phoenix (Elixir's goto for web) and that may be a good start to empower you to make a decision: this video . A great resource for learning Elixir if you choose that route is Programming Elixir 1.2 by Dave Thomas. It's a great book for beginners and can help with you understand Elixir semantics and functional programming.
“you should check out my RailsConf talk on that exact subject”
Author's talk on reasons to migrate from Rails to Elixir/Phoenix.
If you're looking for a reason to migrate from a stack like Ruby/Rails to Elixir/Phoenix you should check out my RailsConf talk on that exact subject: this video
“Good talk in general.”
Covers whether learning Elixir is worth the time.
I started watching RailsConf 2016 - Rails to Phoenix by Brian Cardarella this video as suggested in some comment yesterday and it has some stuff on whether learning Elixir is worth the time. Good talk in general. Edit link to comment thread: link
“you can check out my RailsConf talk on the subject”
Why a company might migrate from Rails to Phoenix.
I posted this in the Elixir 1.3 thread but also relevant here. If you're looking to understand why you/your company may want to consider migrating from Rails to Phoenix you can check out my RailsConf talk on the subject this video
“I spoke about this recently at RailsConf”
Author's RailsConf talk on moving backends from Rails to Phoenix.
We've moved all of our backend offerings from Rails to Elixir/Phoenix. Despite some questioning the value of anything below 100ms response times there is a lot of data backing up the idea that Elixir/Phoenix can lead to a more maintainable and more economical solution. I spoke about this recently at RailsConf: this video Don't get me wrong, I think Rails is an amazing technology but it doesn't fit the use cases and demands our clients have today.
“You may also have a look at”
RailsConf talk on Phoenix versus Rails performance.
> but Erlang/beam code is not that fast. True, no doubt. You wanted a comparison why phoenix is faster than rails. And simply doing things at compile time reduces work at runtime. In Ruby, all Metaprogramming must be done at runtime, for example via method_missing trickery (been there, done that). > Ruby's templates are parsed into code that stays in memory, too, so it's not like they're re-parsed each and every time. This is actually not the same. A single immutable blob of binary (elixir strings) which is shared throughout the whole application can leverage hardware caching better. Jose could answer this probably better than I can do. > someone should dissect these things in a real-world-ish application to see what's actually true. Moz.com recently had fun with Elixir [1]. You may also have a look at this video from latest RailsConf. > The claim was 'fast' though Well at least I know that BEAM processes are far lighter than eg: goroutines. Also there is a per-process GC, so no "stop the world", much smaller units for individual collects, and when a process finishes before the heap grows full, it can be discarded directly. > maintainable, which seems curious given that there are no really old Phoenix apps out there Fair enough. Personally I'd not wait until a software stack is a decade old before even considering it. I have at least worked on Elixir/Phoenix projects for many months now on-off with multiple colleagues, and it was/is still pure joy. Aesthetically pleasing syntax
