We fell out of love with Next.js and back in love with Ruby on Rails

This is part 1 of a series documenting Hardcover’s Alexandria release. We recently migrated our codebase from Next.js to Ruby on Rails, and it’s been amazing so far! It was a learning experience, and I’m excited to share some of our takeaways. I’ll link each article here as it’s written. Introducing Alexandria: Faster, Smoother, Smarter Part 1: How we fell out of love with Next.js and back in love with Ruby on Rails & Inertia.js Part 2: Moving from the Cloud to the Server – Google & AWS to Digital Ocean and Kamal Part 3: How we use Puppeteer to generate OpenGraph images Part 4: Speeding up Ruby on Rails with Solid Cache, server side rendering, Sidekiq, and Brick Part 5: Securing and Speeding up our API Server Today’s focus is on the main reason for the move from Next.js to Ruby on Rails. This is the first question anyone asks, and the most important one. So let’s dive into it. Just a side note: this is going to be a software development related post, not a book related posts. I ... Read full article.