ElixirWeekly

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

Here's what the latest issue looks like:

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

CI Workflows on Tangled for Elixir
Johanna on how to set up CI workflows on Tangled for Elixir, with specific Elixir and Erlang versions, and a PostgreSQL service.

Redis Cluster Support, Without Writing Code
Andrea shares his experiment of building support for Redis Cluster into Redix without writing code, solely relying on AI tooling.

You Don’t Need Kafka: Building Event Driven Systems with GenStage and Broadway
Kiunye on why always defaulting to Kafka is a mistake (and in which situations you might still want to reach for it).

Even more from around the Elixir community

Elixir Wizards: The State of Career Growth in Elixir with Bruce Tate Podcast

Ash Framework in 11 Minutes Video

Static Types Finally Come to the BEAM | Annette Bieniusa & Guillaume Duboc Video

Where Messages Flow Blog post

Let Libraries be Libraries Blog post

LiveStash Performance Tests Blog post

What do we do with Logging in Libraries? Blog post

Exploring LiveView 1.2's Server-composed JS Commands, Colocated CSS, and Colocated Hooks Blog post

Elixir-explorer/explorer released v0.12.0 Project update

ActiveMemory v0.7 - Typed, Attribute-queryable In-memory Store for ETS and Mnesia Project update

Rizwan-khalid-1/api-management-console: Runtime API Route Control for Phoenix Apps — Discover, Toggle, Audit, and Guard Routes from a LiveView Dashboard. 5-second Emergency Shutdowns, no Redeployment Needed. 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).