Very familiar with this problem. This process has happened at my last job and is just starting at my current job. Distributing the issues by team makes a ton of sense, but in my experience, it only gets so far. It’s always been unclear how to handle, and scale, the remaining 10% of on call burden.
Love this post, great exploration of the nuances of uniqueness validations.
I came here to mention that there is also the https://github.com/toptal/database_validations gem which allows you to handle uniqueness validations in Rails in a similar manner to Ecto.
1. apparently a good developer can - optimistically - complete 2000 lines of code a year
2. “not all domains need safety and security”