ElixirWeekly

Get your Elixir News in a weekly email!

Elixir is one of the most vibrant eco-systems in programming right now. There's so much happening and our community is growing faster and faster every day.

ElixirWeekly means: stuff you easily miss, shared on ElixirStatus and the web, handpicked articles and community news in one nice weekly email.

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

Here's what the latest issue looks like:

This week in Elixir

Benchmarking in Elixir
Ready to measure the performance of two pieces of code with the same output? Check out the latest episode: Benchmarking with Benchee!

Halting Plugs in Phoenix
Zachery talks about how he was halting plugs the wrong way and we he found out when discovering the right way to do it.

Supervisors: Building fault-tolerant Elixir applications
Gonzalo takes it a step further by explaining how supervision works in Elixir, and how you can building fault tolerant applications.

ParallelTask: easily run functions in parallel and capture the results
A library for easily parallelizing slow tasks such as API requests, database queries and the like.

Hammer: an elixir rate-limiter with pluggable backends
Hammer is a rate-limiter for Elixir, with a modular backend system, so you can choose where to persist the counters (ETS and Redis right now).

Using GenServer :via
Eric had two GenServers which used the same handle_* interface so he figured out how to talk to both through the same means.

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