A framework that allows to write a domain server, that processes commands and creates events. You should have exactly one domain server for your Rails Disco applications. The domain runs in a domain specific database environment. This helps to make sure no other process interferes wi...

Contains commands, events, validations for Rails Disco. Commands are used to transport updates from Rails to the domain. Validations are used to validate commands in Rails and the domain. Events are created in the domain and processed in projections. Have a look at the rails...

Extensions for active_interaction gem

Google Cloud Pub/Sub adapter and worker for ActiveJob

Make ActiveRecord null model aware.

Contains everything necessary to build and run projection servers for Rails Disco. Projections process events into database models that are optimized for the Rails views. Have a look at the rails-disco documentation on Github for more details.

Exposes a bulk insert API to AR subclasses

Supports binary COPY into PostgreSQL with activerecord

Provides transparent encryption for ActiveRecord. You can protect your data with any encryption algorithm you want.

Save unnecessary round trips to the database

Use PostgreSQL JSONB fields to store association information of your models

Add unsigned option to integer type for ActiveRecord's MySQL2 adapter

ActiveRecord OpenTracing intrumenter

Gives a hook on MySQL warnings that allow you to either raise or log them.

From http://edgeguides.rubyonrails.org/active_record_migrations.html#types-of-schema-dumps: There is however a trade-off: db/schema.rb cannot express database specific items such as triggers, stored procedures or check constraints. While in a migration you can execute cust...

Support for Postgres Notify/Listen

An Active Record extension for Multitenancy with PostgreSQL Row Level Security

Rails ActiveStorage adapter for cloudinary

ActiveTriples provides tools for modeling RDF as discrete resources.

acts_as_account implements double entry accounting for Rails models. Your models get accounts and you can do consistent transactions between them. Since the documentation is sparse, see the transfer.feature for usage examples.