ElixirWeekly

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

Here's what the latest issue looks like:

Issue #225

This week in Elixir

How we Verify Webhooks
Philip from Dashbit wrote this post on how to verify webhooks by building secure client-server communications.

Bringing the Matrix Protocol to Elixir
Niklas has written a post giving a practical introduction to the Matrix protocol with the Matrix Elixir SDK, an open source project he started earlier this year.

Using Event Sourcing and CQRS with Incident - Part 1
Event Sourcing and CQRS are great design patterns for some domains. The Incident library will help implement them without compromising other parts of your application.

Hornet
Ayrat created a new library which handles long-running stress tests gracefully, spawning the optimal number of processes.

Even more from around the Elixir community

Thinking Elixir: LiveView v LiveWire, Alpine.js with Caleb Porzio Podcast

How I Used Elixir Metaprogramming to Clean my Phoenix App Video

Parse XML with NIF Video

Live with Phoenix LiveView and Laravel LiveWire (featuring Caleb Porzio) Video

How to Create a Todo List with Phoenix LiveView Blog post

Adventures in BEAM Optimization for Ably's MQTT Protocol Adapter Blog post

How to Test HTTP Requests in Elixir with ExVCR Blog post

Elixir v1.11.2 released! Project update

Wyeworks/boom 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