Issue #25: visualizing GenStage/Flow, HTTP Streaming and Phoenix React Redux Starter Kit

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

Here's what the latest issue looks like:

Welcome to Issue #25

This is a pretty short issue, which is quiet possibly a result of "the holidays". More importantly, this is the last issue for 2016, and it is also the 26th issue of ElixirWeekly (a Beta Issue #0 was published the week before Issue #1). This means ElixirWeekly is 6 months old now. Wow. Time passed fast.

See you next year!

This week in Elixir

Measuring and visualizing GenStage/Flow with Gnuplot
This is a follow-up to Tymon's last post about tuning GenStage/Flow. This post describes how to measure and visualize the pipeline progress.

Phoenix App deployed into a Load Balanced DigitalOcean setup
Fabio documented a high-availability configuration he wrote for a Phoenix app on DigitalOcean in this step-by-step guide.

HTTP Streaming in Elixir
In this post, Damir describes how his team implemented transparent streaming of HTTP requests directly to a client.

'New' Phoenix React Redux Starter Kit
Another Phoenix starter kit, using React and Redux for the front end. This project contains 5 branches (4 branches + master): master is the base. The other branches contain : Ecto, user support, multi language support, and user + multi language support.

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