JetThoughts has been building software since 2008. Book a call, or write to sales@jetthoughts.com. You'll leave the call with a written one-page scope within 2 working days.
A 30-minute call; pick a time.
Ruby 4.0 YJIT vs ZJIT: Performance Guide
Ruby 4.0 ships two JIT compilers. What YJIT delivers on Rails apps in 2026, the two flags worth tuning, and when the experimental ZJIT is worth a try.
Ruby Fibers for LLM Streaming in Rails
LLM responses stream for 30 seconds while a Rails thread waits. The arithmetic of Puma threads vs open SSE streams, and when Falcon's fibers earn the switch.
Solid Queue: Retries, Concurrency, Monitoring
Solid Queue in production: exponential retries with a cap, dead job alerts, per-record concurrency keys, worker sizing and monitoring, with Rails 8 config.
Falcon in Production: Tuning and Benchmarks
Falcon production tuning: real benchmarks vs Puma, worker-count formulas, memory profiling, GC tuning, connection-pool sizing, and working config examples.
Solid Trifecta: When to Keep Redis in Rails 8
Rails 8 defaults to Solid Cache, Solid Queue, and Solid Cable. Most apps don't need Redis anymore. Some still do. Here's how we decide which workloads stay.
· JetThoughts
Ruby on Rails Performance Optimization Patterns for 2026
Concrete benchmarks and patterns for Rails performance in 2026 - YJIT speedups, Rails 8 query optimization, Redis caching, and N+1 elimination.
· JetThoughts
Laravel + Datadog APM: Setup, Cost, and 3 Alternatives
Datadog APM for Laravel: instrumentation steps, monthly cost at scale, and how it compares with New Relic, Scout, and Blackfire on real benchmarks.
Propshaft vs Sprockets: Migrating the Rails 8 Asset Pipeline
How to migrate from Sprockets to Propshaft in Rails 8. Performance benchmarks, step-by-step migration, and production deployment strategies from teams who have done it.
· JetThoughts Team
Rails 8 Solid Cache: Moving Your Cache Off Redis
Complete guide to Rails 8 Solid Cache performance optimization and Redis migration. Database-backed caching advantages, benchmarks, cost savings, and step-by-step migration strategy.
· JetThoughts Team
Turbo 8 Performance Patterns for Real-Time Rails Apps
What a Turbo broadcast actually costs your server: one render for a stream, one page request per client for a refresh. Plus morphing setup, refresh debouncing, lazy frames and data-turbo-permanent, checked against turbo-rails 2.0.23.
· JetThoughts TeamTell us what you need built