The Operational Monolith
Wrote an article exploring what Rails might look like if it was designed around modern operational constraints from day one.
Wrote an article exploring what Rails might look like if it was designed around modern operational constraints from day one.
Versions 1.19.0 and 1.20.0 brought a set of observability features designed to make debugging and monitoring Rage applications easier. The focus was on giving you control over your logs and visibility into what's happening inside the framework.
Wrote an article exploring some unconventional performance optimizations in Ruby.
Version 1.17.0 introduces Rage::Deferred for background task execution.
Rage was accepted into Cloudflare's Project Alexandria today.
We collaborated with Zuplo on a tutorial for building REST APIs with Rage. The guide walks through creating a full-featured API application from scratch:
TechEmpower Round 23 results are in. Rage shows solid performance improvements over other Ruby frameworks:
Version 1.11.0 brings Rage::OpenAPI for API documentation. The goal was to make documenting APIs less painful - you document your APIs using YARD-style tags, and it generates OpenAPI 3.0 specs automatically.
Version 1.8.0 adds WebSocket support through an Action Cable-compatible API. If you're familiar with Action Cable, the interface will feel immediately familiar - same channels, same broadcasting patterns.
Version 0.7 is a significant milestone - all the features planned for the initial release are now implemented. The framework has the essential pieces in place: