ElixirWeekly

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

Here's what the latest issue looks like:

Issue #231

This week in Elixir

Integrating Travel with Elixir at Duffel
By its own admission, Duffel, at its heart, is building the new operating system for travel. Read how they're using Elixir in this case study.

How to Debug Elixir/Erlang Compiler Performance
Recently someone opened up an issue on Gettext saying compilation of Gettext modules got slower in Erlang/OTP 23. In this article, José shares his investigation.

Using Event Sourcing and CQRS with Incident - Part 2
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.

My Journey With Elixir and Flow-Based Programming: Allan MacGregor
Preslav had quite a conversation with Allan, touching upon topics like Micro-SaaS, flow-based programming, and whether Elixir can help build the next-generation of e-commerce solutions.

Even more from around the Elixir community

Elixir Wizards: Randall Thomas on Learning Elixir and Why Community Matters Podcast

Thinking Elixir: Elixir in Higher Ed with Jonathan Allen Podcast

How the phx_new Project Generator Works Video

Introducing Phoenix LiveSessions Blog post

Social Login with Phoenix 1.5 Blog post

GenServer Process Management/registry Blog post

Using Elixir and Crawly for Price Monitoring Blog post

My Developer Journey into Erlang, Elixir and the Phoenix Framework. Blog post

Creating Unique Constraint/Index Ecto.Migration: Elixir Blog post

Imageflow Elixir Bindings, Along with Ergonomic Elixir-style API Project update

Incident 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