ElixirWeekly

Issue #53 - A naive blockchain implementation in Elixir

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

Here's what the latest issue looks like:

This week in Elixir

How Discord Scaled Elixir to 5,000,000 Concurrent Users
This is the story everyone talks about this week: From the beginning, Discord has been an early adopter of Elixir, now they talk about how they got to 5 million concurrent users.

A naive blockchain implementation in Elixir
A “naive” blockchain implementation to learn Elixir and the basic concepts of the Blockchain.

Announcing Firestorm 0.9
After a long hackathon: Firestorm 0.9 is available on GitHub! Also we’ve deployed the Firestorm official forum, so please come join the discussion!

Designing a P2P Lending platform with Elixir in mind
Andrew has written a long post on how he and his teammates created their first large project in Elixir.

Getting Started With Phoenix v1.3
Michael provides a gentle introduction to Phoenix for those with a basic understanding of Elixir where readers build the backend of a rostering system.

A Year with Cachex in Production
Isaac wrote up his thoughts about the first year of Cachex.

Learn Elixir The Beast Mode Way
Zed Shaw writes about how he just maybe write a book about Elixir. As a fan of the "That Hard Way" series, I liked his remarks!

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