ElixirWeekly

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

Here's what the latest issue looks like:

Issue #171

This week in Elixir

Batching for Operations with Elixir and Broadway
Take a deep-dive into Broadway as Michael builds a simple data pipeline, and then improves its efficiency by using batchers.

ElixirTalk - Lumen!
The fine folks of ElixirTalk sat down with with the fine folks from DockYard to talk about Lumen, the new Elixir compiler that targets WebAssembly!

Stream.unfold/2
Lasse wrote a great introduction to Stream.unfold/2, introducing the concept of Fibonacci as a Service :-)

Ecto & Multi-tenancy - Dynamic Repos - Part 1 - Getting Started
Multi-tenancy was trickier than Lars thought it would be. This post covers the basics.

edisonywh/committee
Committee is a supercharged git hooks manager in pure Elixir that allows you to manage your git hooks like pre_commit by writing just Elixir.

Elixir v1.9.2 has been released
Please refer to the CHANGELOG for the patch notes.

Even more from around the Elixir community

The Changelog #365: Let's Talk Elixir! with Chris Bell and Desmond Bowe Podcast

Elixir Mix: Application Monitoring Using Telemetry With Arkadiusz Gil Podcast

Elixir Talk: Desmond's new Job, Managing Complexity, and Designing Systems Podcast

Rate Limiting Continued - 2019-10-14 - Live Coding Grapevine Video

Generating RSS Feeds with Elixir Video

ElixirConf EU 2020 Accepts Training Proposals! Conference

BEAM FOSDEM Conference

Locally Evaluating Azure ARM Templates Blog post

String Length in Elixir Blog post

MyTopdogStatus by Basia Trojecka Blog post

What's the Difference Between Alias, Import, Require and use in Elixir? Blog post

sobolevn/ecto_autoslug_field Project update

KronicDeth/intellij-elixir Project update

Submit your blog post/project update

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

ElixirWeekly by @elixirstatus

ElixirWeekly

Questions & Answers

Contact