Why Lago Continues Using Ruby on Rails for API Development in 2025
By
FinnLobsien
A bagel you'd recommend to a friend without hedging.
Summary
Lago, a company handling millions of API calls daily, explains why they continue to use Ruby on Rails in 2025 despite newer programming languages being available. The founding team chose Rails for its development speed and their extensive experience with the framework. While they've incorporated Go and Rust where appropriate, they maintain that Rails remains the optimal choice for rapid product development and shipping.
Key quotes
· 5 pulledWhen we started Lago, we picked Ruby on Rails for our core API. The choice was obvious because our founding team had decade of Rails experience.
Rails was the fastest way we could build an API product.
Today, we've receive millions of API calls a day. We've upgraded through multiple Ruby/Rails versions.
But if we were starting today, in 2025, we'd still choose Rails.
The boring superpower: shipping speed
You might also wanna read
RUSTWA: Unofficial WhatsApp Web API Built in Rust for Automation
RUSTWA is an unofficial WhatsApp Web API built in Rust that provides essential WhatsApp automation features without unnecessary complexity.
Product Hunt·4mo ago
Why Average LLM Use Is Likely Destroying Value in Software Development
The author argues that, contrary to prevailing hype, the average use of Large Language Models (LLMs) is likely destroying value rather than
unessays.substack.com·11h ago
How AI Accelerated Prototyping: From Idea to Tangible in Record Time
The author reflects on how AI has transformed their prototyping workflow. Previously, the biggest bottleneck was the time needed to scaffold
darylcecile.net·11h ago
GitLab 19.0 launches with Secrets Manager, agentic workflows, and self-hosted AI models
GitLab 19.0 has been released, positioning itself as an intelligent orchestration platform for DevSecOps. The release includes expanded secr
bit.ly·1d ago
Centralizing Error Handling in Rust with Custom AppError Enums
This article discusses the importance of centralizing error handling in Rust applications using a custom AppError enum combined with map_err
Zig Devlog: Build System Rework Separates Maker and Configurer Processes
This devlog entry from the Zig programming language project announces a major rework of the build system, separating the maker process from
ziglang.org·1d ago