Issue #23: Many to many upserts, Measuring Temperature on a Raspberry Pi and Connecting to a remote Elixir node deployed with Distillery

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

Here's what the latest issue looks like:

This week in Elixir

How Discord handles push request bursts with Elixir’s GenStage
Easily the most compelling piece of the week. To handle Discord's growth, its engineering team had to figure out how to scale the backend services. Spoiler: Elixir gets a mention or two.

Many to many and upserts
This is an excerpt of Plataformatec's ebook “What’s new in Ecto 2.0 (beta version)” in which José Valim presents `Ecto.Changeset.put_assoc/4` in contrast to `cast_assoc/3`.

Elixir foundations for Ruby Devs: Transforming Data
In an unexpected soft-dring analogy Tomasz compares writing Elixir with a Ruby mindset to drinking water, just to realize that it is actually Sprite.

Connecting Ruby and Elixir with Erlectricity
Communicate between Ruby and Elixir using Erlang Ports and Erlectricity.

Project ExCelsius: Measuring Temperature on a Raspberry Pi
A Nerves powered Raspberry Pi reads temperature from a DS18B20 sensor via the 1-wire protocol. Very nice read!

Connect to a remote Elixir node deployed with Distillery
When building Elixir apps with Distillery you don’t install Elixir on the server as Distillery bundles everything it needs. But what if you want to have a peek inside using Observer?

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