or subscribe with
Join 3,000+ readers for one email each week.
Digests » 120
AppSignal: Elixir’s first error monitoring and performance tool.
this week's favorite
Most web-apps in production probably need some kind of rate-limiting, to prevent rough clients from taking down the app by flooding it with expensive http requests. In this article we’ll see how to add rate-limiting to an Elixir/Phoenix application, using the Hammer package. We will also see how to switch the hammer backend so that it stores it’s data in Redis.
It’s been a big weekend! The new formatter that José mentioned in his ElixirConf talk is finally here! It landed on Sunday, and that means we can now poke around in the code to see everything that it does and answer a few burning questions.
Welcome back! This time we’ll focus on how to generate and surface our API’s documentation, adding a route to help explore, and update our tests against the specification we generate! We’re in for a ride.
I’ve been cooking up a side project recently that involves crawling through a domain, searching for links to specific websites. While I’m keeping the details of the project shrouded in mystery for now, building out a web crawler using Elixir sounds like a fantastic learning experience.
When starting banana, we had to decide which tool we would use to build our backend system. We had experience in many different languages and frameworks such as Ruby on Rails, Node.js, Go, Python, and Java, but we decided to try Elixir and the Phoenix framework.