Issue #30: Comparing Go and Elixir

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

Here's what the latest issue looks like:

This week in Elixir

Comparing Go and Elixir
This post compares Go and Elixir by taking a look at their backgrounds, their programming styles and how they deal with concurrency.

Configuring NGINX for Phoenix applications
Using NGINX as a front-end proxy for web applications is a pretty standard setup. There are some things to keep in mind concerning Phoenix, SSL, and asset delivery and this article sums up the details.

Deploying Phoenix Apps for Rails developers: Part 2
In this post Alex shows us how to deploy an upgrade to a distillery release and use Erlang’s hot code upgrades.

Create a riak_core application in Elixir: Part 2
This is the second part on how to implement a distributed and fault- tolerance application with riak_core and Elixir.

Mocks and side effects
This post describes a pattern for implementing code with side effects in a testable way in Elixir.

Playing with Pipes
A look at how pipes can work with things like the if function. Do not try this at home!

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