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

Here's what the latest issue looks like:

Logo ElixirWeekly by @elixirstatus Issue #241
This week in Elixir

How Atom Keys with JSON in Ecto can Break Your System
Patryk shows us what you need to know if you use the map type in your Ecto schemas.

How to use Ecto’s Repo.stream/1 to Process Large Amounts of Data
Maciej wrote this post about how it’s great to have tools like Flow, GenStage, or Broadway, but why we don’t always need them!

Elixir in Production: Papercups
What are the benefits of Elixir for SaaS products? Find the answer in this interview with Alex from Papercups.

A Telegram bot in Elixir
This post by Lars is a getting started step-by-step guide in setting up an Elixir-based Telegram bot.

Even more from around the Elixir community

Elixir Wizards: Brian Howenstein on How ClusterTruck is Innovating Food Delivery Podcast

Thinking Elixir: Using LiveView and Hooks with Alex Minette Podcast

Beam Radio Podcast

Encrypting Ecto Fields with Cloak Video

Autostarting Crypto Prices Streaming - Create a Cryptocurrency Trading bot in Elixir - Episode 13 Video

One Year of Elixir: How It Compares to Ruby Blog post

Binary WebSocket Communication with Elixir & Phoenix Blog post

Dynamic Nested Function Call Blog post

Securing Webhook Payload Delivery in Phoenix Blog post

Dynamic Ecto Queries Blog post

Building an Event-sourced Game with Phoenix Liveview: Acting on the Game from the Views Blog post

Build ‘availability First’ Systems with Elixir + DataStax Astra Blog post

Why Elixir is the Programming Language You Should Learn in 2021 Blog post

Why Choose Elixir? Blog post

Incident Project update

influxdata/mix_test_interactive 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 :)


Feedback? Questions? Anything else?

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