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

Here's what the latest issue looks like:

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

Building a new MySQL Adapter for Ecto Part IV: Ecto Integration
Part 4 of Wojtek's series about building MyXQL, the new MySQL goodness for Ecto!

Small is Beautiful - The Component Library
Dave finally released his much discussed concept of "components" as an Elixir library.

First Month of Functional Programming in Elixir
Coming from an object-oriented background using mostly Java and Javascript, Elixir syntax and structure is both familiar and not.

How We Used Elixir's GenServers + Dynamic Supervisors to Build Concurrent, Fault Tolerant Workflows
The fine folks at The Flatiron School wrote about their experience while leveraging Elixir's GenServers and Dynamic Supervisors to deliver large amounts of content to their students.

[VIDEO] Phoenix Contexts
This is a great episode of ElixirCasts for anyone new to Phoenix or wanting to see how contexts work.

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


Feedback? Questions? Anything else?

Please contact René Föhring (email or tweet @rrrene for a quick conversation).