ElixirWeekly

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

Here's what the latest issue looks like:

Issue #321

This week in Elixir

8 SaaS Using Elixir and Phoenix in Production
Here are some of the most interesting examples of SaaS companies using Elixir and Phoenix as the basis of their technology stack.

Telemetry UI
A lot of popular Elixir packages come with a built-in integration of Erlang’s telemetry system. Simon shows us how to use Telemetry UI to visualize the resulting metrics.

Fix Process Bottlenecks with Elixir 1.14's Partition Supervisor
In this post, the fine folks at AppSignal are exploring Elixir’s new PartitionSupervisor and are taking a look at some code that suffers from the exact bottleneck issue that partitions supervisors are designed to solve.

Elixir Code Style, a Brief Example
A short blog post by Michael showing two ways to write a function, and why one style is better than the other.

Debugging Elixir Phoenix with Dbg
Learn how the new dbg can replace IO.inspect to enhance your debugging workflow.

Even more from around the Elixir community

Elixir Conf Uruguay Conference

Sonic Pi - Live. Code. Music. Video

Thinking Elixir: PhxLiveStorybook Podcast

How I Deploy my Phoenix Apps Blog post

Organize Your Tests with Context Tags Blog post

Tech: Why I Chose Elixir and Elm for Picture It Blog post

How to Speed up Your Elixir Compile Times (Part 3) Blog post

How to Implement a Disk Cache Plugin for Elixir's Req HTTP Client? Blog post

LiveView Native (Almost) Weekly #2 Blog post

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