Digests » 100
Receive deep insights about Elixir, Phoenix and other developments.
Over the last few months I’ve been working in Elixir and its most popular web framework Phoenix. During this time I built “Houston”, a deployment tool written in Elixir/Phoenix to help make deploying at TpT easier by providing a simple uniform interface to all of our Jenkins Pipelines.
Many Elixir programmers have probably heard references to "ets" or "ETS" in talks, or may have seen calls to the Erlang :ets module in code, but I would wager the majority haven't used this feature of Erlang in practice. Let's change that.
In this example, we will work through a typical app feature: exporting database records as CSV files. It’s a useful feature and is a good example to show how versatile Elixir streams can be.
First, there aren’t “partials” in Phoenix as we know them in Rails. As most parts of Phoenix, things are more explicit. You just render a template in the context of a specific “View” module. That’s all.
First of all, I need to address that answer previously posted by someone else that claims Ruby on Rails can’t scale, and you should be using Elixir “if your app needs to scale”.