A utility for quering interface to any objects like ActiveRecord. This gem support for querying, association, enum, and relation.

An out of box API built for Rails.

Provide export / import to ActiveRecord

Provides async methods ruby objects for queuing background jobs. Currently supports Resque. Bonus: callback hooks for ActiveRecord objects

Provides utility classes, helpers and decorators to the AWS Ruby SDK v2

Managing aws resources with active way.

ActiveResource, but with a caching layer.

Module for caching results of method invocations.

Ruby wrapper around active campaign api

ActiveCampaign REST API

Chronicle integrates Datomic into Ruby on Rails Active Record, providing seamless CRuby/JRuby transport auto-detection, immutable time-travel queries, and cross-database ACID transaction coordination.

active_cipher_storage encrypts and decrypts Rails Active Storage files with AES-256-GCM envelope encryption. It supports AWS S3, streaming downloads, multipart uploads, AWS KMS, environment-variable keys, and custom key providers for Ruby and Rails applications.

A basic Ruby SDK to interact with the Active Collab API.

ActiveCommand adds the ability to use the command pattern commonly seen in CQRS.

This gem provides a macro for comparing the column and the other column of the record. Type of the comparable column is Date Time Numeric, and all that jazz.

Active Component introduces components into your Rails presentation layer. The use of components improves consistency and development speed through reuse and a new way of view code organization. Components are plain Ruby classes that are able to render themselves using a to_html method. Active Component provides several means that make it easy to write and use components.

Trim the fatty models. Use ActiveContainer.

Steroid command pattern.

Schemaless models in Berkeley DB.

ActiveDurable runs multi-step business flows (checkouts, onboarding, payouts) as durable sagas stored in your own database. Completed steps are checkpointed and never repeated after a crash, failures before the point of no return are compensated in reverse order, and failures after it are retried. No Redis and no extra servers: just Active Record and Active Job.