ElixirWeekly

Issue #100 - Introducing Horde - a Distributed Supervisor in Elixir

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

Here's what the latest issue looks like:

Logo ElixirWeekly by @elixirstatus Issue #100
Welcome to Issue #100

Wow. 100 issues of ElixirWeekly. Time has flown.

This week in Elixir

Introducing Sage — a Sagas Pattern Implementation in Elixir
Distributed transactions are hard and expensive, if you wonder how to pragmatically handle them in a mid-size project— this article is for you.

Introducing Horde - a Distributed Supervisor in Elixir
Horde is a distributed supervisor and a distributed registry, built using the magic of delta-CRDTs. Read how Derek built it.

From Web Application to Distributed System
This blog post shows how to develop a web application that can “simply” scale to a distributed system.

EMPEX: Keynote by Dave Thomas
In this video from the EMPEX conference, Dave challenges the current state of Elixir and suggests alternatives for concepts like applications and the implementation of GenServers.

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

Contact

Feedback? Questions? Anything else?

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