ElixirWeekly

Issue #133 - Avoid These OTP Supervision Performance Pitfalls

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

Here's what the latest issue looks like:

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

[VIDEO] Elixir Components: A 12 minute introduction
Dave put together a 12 minute video showing some aspects of his Component library.

Avoid These OTP Supervision Performance Pitfalls
Jose recently dropped a gem on elixir-lang-core, which was non-obvious and Derek turned it into a blog post!

How To Get Struct Type In Elixir
Three ways on how to quickly get the type of a struct in Elixir.

Serving Plug: Building an Elixir HTTP server from scratch
To understand how HTTP servers work, let's implement a minimal example of one that can run a Plug application.

What’s going on in libcluster? (Elixir library overview)
Joseph illustrated and annotated Paul's famous libcluster library!

Putting Phoenix in an iframe
... might be easier (or harder) than you think.

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).