Articles about Ruby On Rails .

Last week we published the case study of one of the first projects of ours. After 10 years in the archive I found and brought this old Ruby on Rails 4.0 application back to life.

What is Hybrid and Dynamic Database Multitenancy and how to successfully achieve it with Ruby on Rails (> 6.0) and PostgreSQL? Our experience implementing a hybrid and dynamic database multitenancy system for one of the projects we're involved.

There's a lot of cristiscim to Ruby and Ruby on Rails. In this post we will try and debunk four widespread myths about Ruby.

Ruby on Rails is our main tool for building MVPs and big web applications. There's a wide-array of myth's about it online: that it's old, or dead, or slow, that it's not relevant anymore. We revisit our tech choice every year and we still chose Ruby on Rails. Here's why.

Do you have a Ruby or Rails application in production for more than 4 or 5 years? Has the test suite crumbled to pieces because too many broken or flaky test that no one has time to fix? Do you feel your app is needing a lot of love that no budget will ever be able to sustain? Read on to know what we do in these cases.

When maintaining Ruby on Rails applications, it's always recommended to run the latest versions of the framework so it receives security patches and performance boosts from newer versions. In this post we'll see our way of upgrading Ruby on Rails applications.

Based on Ruby on Rails examples, the core idea should be applicable to other languages and frameworks.