In our last post, we examined the most common ways to organize business logic in Ruby on Rails. They all have advantages and drawbacks, and essentially, most do not leverage the full power of Object Oriented Programming in Ruby. This time, we will introduce another alternative that more naturally fits the mental models we apply when reasoning about the behavior of our applications: DCI.
Puppeteer is a powerful browser automation library for web scraping and integration testing. However, the asynchronous, real-time API leaves plenty of room for gotchas and antipatterns to arise. This article is part of a series, starting with Avoiding Puppeteer Antipatterns and Puppeteer in Node.js: Common Mistakes to Avoid. In this post, we'll add another dozen antipatterns to the list. There will be no overlap with previous installments, so you may wish to start with those.
As a developer supporting a growing business, you’ll likely spend a lot of time thinking about scaling. We live in a wonderful time to be solving scale problems. Computers are so fast and capable that many of the development decisions you make when writing backend systems won’t noticeably impact performance(until your app reaches an absolutely massive scale). If this weren’t the case, we’d all be writing web servers in C.
In our introduction to Absinthe, we covered the basics of Absinthe and GraphQL for an Elixir application. Now we'll dig deeper and see how we can customize Absinthe for larger-scale Elixir applications. Let's get going!
In this article, we'll introduce Ruby on Rails' lesser-known but powerful cousin Sinatra. We'll use the framework to build a cost-of-living calculator app. By the end of the article, you'll know what Sinatra is and how to use it. Let's go!
In the first article of this series, we introduced Fastify and compared it to Express, highlighting the benefits of switching to Fastify for high-performance web applications. We also explored Fastify's plugin system in detail, showing you how to extend and customize your web applications with reusable modules. In this part, we'll dive deeper into some of Fastify's more advanced concepts.
Ecto can be considered the standard database wrapper and query generator for Elixir, enabling developers to interact with databases efficiently. However, inefficient queries or misconfigurations still can (and will) happen. Addressing these issues is crucial for a smooth user experience.
Logs are essential to any application's development. Most Ruby logs are verbose and chunky, so digging for exactly what you need can be difficult. Even though they contain useful information, you might not get as much value as you should from logs if you don't know how to use them effectively. In this article, we'll explore: Let's get started.
Node.js 12.x onwards introduced async stack traces. Async stack traces allow developers to view the call stack of asynchronous code, making it easier to trace and debug code issues. In this post, we’ll see how async stack traces work, how you can use them to debug code, and how to track them using AppSignal. Ready? Let's get going!
Absinthe is a toolkit for building a GraphQL API with Elixir. It has a declarative syntax that fits really well with Elixir’s idiomatic style. In today’s post — the first of a series on Absinthe — we will explore how you can use Absinthe to create a GraphQL API. But before we jump into Absinthe, let’s take a brief look at GraphQL.
