There is a pattern I am very fond of - “one database per tenant” in web applications with multiple, isolated users. Recently, I needed to fix an application I had for a long time where this database-per-tenant multitenancy utterly broke down, because I was doing connection management wrong. Which begat the question: how do you even approach doing it right? And it turns out I was not alone in this. The most popular gem for multitenancy - Apartment - which I have even used in my failed star...| Julik Tarkhanov
This is my personal site, where I write about Ruby, programming, and any of my varied fascinations.| fractaledmind.github.io
This is my personal site, where I write about Ruby, programming, and any of my varied fascinations.| fractaledmind.github.io
Shop app horizontally scaled a Ruby on Rails app with Vitess. This blog describes Vitess and our detailed approach for introducing Vitess to a Rails app.| Shopify
Testing Rails ApplicationsThis guide covers built-in mechanisms in Rails for testing your application.After reading this guide, you will know: Rails testing terminology. How to write unit, functional, integration, and system tests for your application. Other popular testing approaches and plugins.| Ruby on Rails Guides
Learn how to create and implement a row level security policy in Rails, allowing to limit the database rows a user can access.| pganalyze
Put your data where your users and applications are.| planetscale.com