Every Thursday: No frills, no click-through, no spam.

Here's what the latest issue looks like:

Logo ElixirWeekly by @elixirstatus Issue #222
This week in Elixir

Automatic and Manual Ecto Migrations
Should you have both schema and data migrations? Should you run migrations automatically or manually? Wojtek shows us how to mix and match approaches and get the best from each scenario.

Real Time Communication at Scale with Elixir at Discord
It is mindblowing how Discord handles so many users with Elixir and such a small team! They're also my goto-answer to the question: "Does anybody use Elixir?"

Capabilities of Elixir's Logger
This post demonstrates how logs work in Elixir, jumping into Elixir’s Logger module, which brings a lot of power to logging features. It also smoothly integrates with Erlang’s :logger to convert code to Elixir syntax.

Lumen: Update up to 2020-10-13
Did you know they post regular updates about the progress of the Lumen compiler (which will basically enable Elixir in the browser)?

That's it for this round, have a great day!
@rrrene from ElixirWeekly

If you like this newsletter, please tell the world!

You can view this issue in your web browser.

You can subscribe below:

Questions & Answers

Can I submit things I made to be included in the next issue?

Yes! Simply post them to ElixirStatus and you can be sure that they land on my radar.

Is my email address safe with you?

Yes. I'd like to consider myself a trustworthy individual, but then who doesn't?

I am, however, an active member of the open-source Elixir community and the maintainer of Credo and ElixirStatus. I will NOT ruin my reputation by selling your data to a third party.

Why do you require me to confirm my email address?

I just believe that requiring double opt-in to subscribe to any email-based system is a win for both parties: You are safe from unintentionally subscribing and I can be confident that you actually own the email address and want to receive the newsletter I send you :)


Feedback? Questions? Anything else?

Please contact René Föhring (email or tweet @rrrene for a quick conversation).