<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Elixir on Personal Blog of Maximilian Ehlers</title><link>https://blog.sodawa.com/tags/elixir/</link><description>Recent content in Elixir on Personal Blog of Maximilian Ehlers</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 16 May 2019 16:22:00 +0000</lastBuildDate><atom:link href="https://blog.sodawa.com/tags/elixir/index.xml" rel="self" type="application/rss+xml"/><item><title>Moving the freelytics API from Golang to Elixir</title><link>https://blog.sodawa.com/blog/moving-the-freelytics-api-from-golang-to-elixir/</link><pubDate>Thu, 16 May 2019 16:22:00 +0000</pubDate><guid>https://blog.sodawa.com/blog/moving-the-freelytics-api-from-golang-to-elixir/</guid><description>You might have read https://ehlers.berlin/open-analytics-a-new-approach/, where I talk about a recent project I started.
In my initial design I chose Elixir as the language that fits best. Via the BEAM VM and the Erlang OTP it can easily handle a massive amount of requests, where some will surely fail and it would nonetheless keep on running almost indefinitely. In addition I can live patch the running system, scale it up, inspect it etc.</description></item></channel></rss>