Issue #27: Registry in Elixir 1.4, Passwordless Authentication in Phoenix and Protecting Your Data with PostgreSQL Constraints

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

Here's what the latest issue looks like:

This week in Elixir

Elixir v1.4 released
Congrats to the Elixir Core team and all contributors!

Registry in Elixir 1.4
One of the new additions in Elixir 1.4 that everyone's been looking forward to is the new Registry module. Here's one way to take advantage of this handy feature that is now part of the core library.

Building a CQRS/ES web application in Elixir using Phoenix
Ben describes how he built a web application following a Command Query Responsibility Segregation/Event Sourcing (CQRS/ES) pattern in Elixir.

Passwordless Authentication in Phoenix
Passwordless or “magic link” authentication is very user friendly, relatively easy to implement, and sufficiently secure for most apps. This article is a step by step guide for implementing passwordless authentication in Phoenix.

Protect Your Data with PostgreSQL Constraints
Ecto embraces database constraints as the correct way to guarantee consistency in your database. But do you know how to use them?

Molasses - A feature toggling library for Elixir!
A feature toggle library for Elixir, which allows you to roll out select features to a subset of your users (e.g. for beta testing).

Learn Elixir with a Rubyist - Episode III
This time: Maps, Functions + Pattern Matching = ❤️!

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).