Issue #163 - The Dangers of the Single Global Process
Every Thursday: No frills, no click-through, no spam.
Here's what the latest issue looks like:
This week in Elixir
Use Github CI for Elixir Projects Elixir
Github launched "GitHub Actions" which make it possible to perform CI without leaving the place where the code belongs. This blog post shows how to configure GitHub Actions for an Elixir project with external services.
The Dangers of the Single Global Process
In this article Keathley discusses some of the dangers of trying to maintain state in a single, unique process. He also presents some solutions to these problems as well as some alternatives.
Authenticate Github's Webhooks API Using Elixir's Plug
Jeremy talks about his journey authenticating Github's webhooks API with a simple Plug. I really like this idea as an alternative to the usual first-project-in-new-language ideas.
Prometheus, PostGIS and Phoenix Part 1
Learn how to set up and use Prometheus+Grafana to monitor a PostGIS backed Phoenix application in this 2 part series!
The RealReal - Elixir Adoption Story
In this video, José Valim (co-founder, Plataformatec) interviews Fredrik Björk (CTO, The RealReal) for the story of why and how The RealReal adopted Elixir.
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).