[I still do not have permission to make a new topic from an existing post]
I have my program split up into a set of Modules, each module has a Router, which is called from the main Router like:
use MyServer.Routers.MyModule, base_scope: "/mymodule"
And those routers implement behaviours, and they have a set of callbacks such as building a menu drop-down on the top titlebar, setting a page title, etc… It seems very elixir’ish to me and easy to extend (or remove if I need to bulk-remove a module).
At DockYard, we transitioned our backend development from Ruby and Rails to Elixir and Phoenix once it became clear that Phoenix better served our clients needs to take on the modern web. As we’ve seen, Phoenix is Not Rails, but we borrow some of their great ideas. We were also delighted to give back in the other direction when Rails announced that Rails 5.0 would be shipping with Action Cable – a feature that takes inspiration from Phoenix Channels.
A blog post describing mix reph.new task which is very similar to phx.new and based on Phoenix 1.3 installer, but aims to scaffold React/Phoenix-stack based apps.
Here’s the story of complex process of researching, evaluating, choosing and introducing Elixir to cozy yet shrinking world of complex Rails monolith at Shedul - a global salon booking system.
I’ve just posted this in the Elixir Blog Posts and I’ve just find out this thread, which seems more appropriate for this post.
In this article we see how to solve an issue we faced in the previous article, scaling horizontally the Phoenix Chat app. We’ll see how to integrate the PubSub Redis adapter to our chat app, and make it distributed.
