Skip to content
0:00 / 0:00

#rack#rubyonrails#middleware

RailsConf 2017: Rack ‘em, Stack ‘em Web Apps by Jason Clark

Confreaks

42K subscribers • 74 videos on Hallway • Conference channel

YouTube
  • Recommended by 1 person: 1 on Stack Overflow and its sister sites.
  • Presented by Jason Clark
  • May be out of date. Uploaded 9 years ago, in an area where tools change fast.

Intermediate. Assumes working knowledge.

711 views9 years ago1 recommendation

Web developmentProgramming languagesRubySoftware architecture

Jason Clark explains the Rack HTTP library from top to bottom, showing how to build APIs and write reusable middleware.

RailsConf 2017: Rack ‘em, Stack ‘em Web Apps by Jason Clark While Rails is the most common Ruby web framework, it’s not the only option. Rack is a simple, elegant HTTP library, ideal for microservices and high performance applications. In this talk, you’ll see Rack from top to bottom. Starting from the simplest app, we’ll grow our code into a RESTful HTTP API. We’ll test our code, write reusable middleware, and dig through what Rack provides out of the box. Throughout, we’ll balance when Rack is a good fit, and when larger tools are needed. If you’ve heard of Rack but wondered where it fits in the Ruby web stack, here’s your chance!

Why it's here

1 person recommends this

What people say. Recommended as an excellent visual explanation of how Rack middleware sits between web servers and frameworks.

Vbpon Stack Overflow • Recommends

On “What is Rack middleware?”

Rack is a gem which provides a simple interface to abstract HTTP request/response. Rack sits between web frameworks (Rails, Sinatra etc) and web servers (unicorn, puma) as an adaptor. From above image this keeps unicorn server completely independent from knowing about rails and rails doesn't know about unicorn. This is a good example of loose coupling, separation of concerns. Above image is from this rails conference talk on rack link to this video I recommend watching it for deeper understanding.