rodauth-oauth VS sequel-activerecord_connection

It depends on what you mean by OAuth 2.0. If you want your app to be an OAuth 2.0 provider, then you'd use rodauth-oauth. If you want to enable your users to login through external apps that implement the OAuth 2.0 protocol, then OmniAuth is what you'd use. Not all external apps implement login via the OAuth 2.0 protocol, those that do will have their OmniAuth strategies inherit from omniauth-oauth2.

I want to make it easier for 3rd-party Rodauth extensions to provide migrations/views for Rails generators. The rodauth-oauth gem currently provides its own generators (rodauth:oauth:install and rodauth:oauth:views), but it would be nice if they didn't have to be duplicated.

For the integration to work, I would need to make Sequel reuse Active Record's database connection. I discussed this idea with Jeremy Evans (the lead Sequel maintainer), and he provided me with some guidance, thanks to which I was able to come up a solution. It was a Sequel extension that retrieved Active Record connections, kept transaction state and callbacks synchronized between Sequel and Active Record, integrated SQL instrumentation, and reconciliated adapter differences (see my previous article for more details).

Our Rails app at work is using Active Record, but I started non-apologetically using Sequel for any features I'm missing from Active Record, because I don't have the patience for Active Record to catch up. For our analytics database we're using only Sequel, because AR was missing too many features (see my article), while for our main database we're using it in tandem with Active Record, reusing Active Record's database connection. I'm pretty happy that the latter is now possible, as it gives people the opportunity to try out Sequel without any overhead.

The way I look at it, a pure Active Record implementation could never be fully complete. That's why I instead chose the path of making Sequel integrate seamlessly with Active Record, by sharing a database connection as /u/honeyryderchuck said, hooking into Active Record's query instrumentation, and also by making Sequel transactions interoperable with Active Record's. It's also worth noting that core Sequel is significantly lighter than Active Record.

the main impediments to my using sequel in Rails are: authentication - which has largely been solved. Janko has written a gem allowing for rod auth to be used with rails, easily. https://github.com/janko/rodauth-rails - i believe he has also written another gem to make it easy to use sequel in a rails app https://github.com/janko/sequel-activerecord_connection

From a user's perspective, I've always found the fact that rom-sql uses Sequel under-the-hood as a big advantage. For someone who is familiar with Sequel it lowers the barrier of understanding how rom-sql works. And it's possible to leverage many of Sequel's useful features that rom-sql might not support OOTB (including performance optimizations such as sequel_pg), even if that requires dropping to the Sequel database level. When I announced sequel-activerecord_connection, one of the questions I received was whether that will work with rom-sql too (and it does).