There’s no reason why you have to couple storage interface to business logic. I’ve done this before. Develop business logic as a separate gem and then include

There’s no reason why you have to couple storage interface to business logic. I’ve done this before. Develop business logic as a separate gem and then include that in a Rails project. ActiveRecord is actually entirely optional in Rails, it’s just the default. You can also use POROs as presenters and mixin ActiveModel if you want things like validations. Then couple that with Sequel as an alternative to ActiveRecord to run data access objects. Sequel is often regarded as a more permanent alternative to ActiveRecord. It’s not a drop in replacement though so that might be a consideration for team skills/support.