AppSignal helps teams build better applications. We track errors and performance, monitor hosts and offer a metrics platform. Our blog features news, product updates and articles from our team. If you are interested in contributing to our blog or have an article idea, send us a message!
By Jeff Kreeftmeijer on
Instead of counting the associated records in the database every time the page loads, ActiveRecord’s counter caching feature allows storing the counter and updating it every time an associated object is created or removed.
read moreBy Jeff Kreeftmeijer on
Elixir uses GenServers to keep state and run code asynchronously. But how does this work? In this episode of Elixir Alchemy, we'll deconstruct Elixir's GenServer module to see how it works under the hood.
read moreBy Thijs Cadier on
We've talked about the retry keyword before. Its little-known counterpart redo works similarly, but reruns loop iterations instead of whole blocks.
read moreBy Jeff Kreeftmeijer on
Ruby's handling of enumerables is one of it's most magical features. In this episode of Ruby Magic, we'll learn how these work and how to make your own objects tenumerable.
read moreBy Jeff Kreeftmeijer on
Turbolinks is an optimization that increases the perceived performance by being smart about switching pages and reloading assets in your app.
read moreBy Jeff Kreeftmeijer on
Besides `rescue`, Ruby has more ways to handle exceptions. We'll use the `retry` and `ensure` keywords and reraised exceptions to build a resilient web API client.
read moreBy Tom de Bruijn on
We've released a new gem version that allows you to filter more data and set the app revision in the config.
read moreBy Roy Tomeij on
AppSignal is GDPR compliant. This is what we changed, and how using AppSignal as your Data Processor enables you to be compliant too.
read moreBy Jeff Kreeftmeijer on
We've released a new Elixir package that allows you to filter more data and set the app revision in the config.
read moreBy Jeff Kreeftmeijer on
Rails' conditional GET support allows you to store rendered pages in the user's browser cache to reuse them for repeated requests instead of rendering the same view multiple times.
read moreBy Jeff Kreeftmeijer on
The N+1 queries problem is a common, but usually easy to spot, performance antipattern that's sometimes caused by lazy loading associations.
read moreBy Robert Beekman on
For the first time in years we lost customer data, here's how it happened.
read more
Magicians never share their secrets. But we do. Sign up for our Ruby Magic email series and receive deep insights about garbage collection, memory allocation, concurrency and much more.