A look at how Ruby interprets your code and how you can use this knowledge to your advantage.

A deep dive into achieving concurrency using an event loop.

A deep dive into achieving concurrency using threads.

A deep dive into achieving concurrency using multi-process.

After starting work on a simple HTTP server a while back, we're diving back in to learn how to handle POST requests and what we need to do to serve a Rails application.

Escaping characters in Ruby can be quite confusing. In this post we'll cover the power of the backslash symbol \ and how you can use it.

Web servers, and HTTP in general, might seem difficult to understand. In this Ruby Magic episode we'll learn how a to build a simple Ruby HTTP server in 30 lines of code

Make sure your exception handling is done right. Get up to speed with this Ruby Magic primer and make sure you only rescue the exceptions you need to.

In the previous episode of Ruby Magic we talked about why we need Garbage Collection (GC) and how it works in general. Now we'll dive a bit deeper into how this is implemented in Ruby.

Whenever you run your code, you use memory. But you never have to think about how to clear memory again afterwards. How does this work?

Multiple people will use your app at the same time, and you want to deliver your app as fast as possible. So you'll need some way to handle concurrency. Fear not! Most webservers already do this by default. But when you need to scale, you want to use concurrency in the most efficient way possible.