umbrellio/table_sync
54.6
Adequate · 8 November 2026
2.2k
lines of production code
Ruby
primary language
7
measurements over time
What this system is
TableSync is a Ruby gem designed for bidirectional database table synchronization between microservices. It operates by listening to model events and publishing changes via RabbitMQ, supporting both ActiveRecord and Sequel ORM adapters. The system features configurable publishing and receiving pipelines with options for debouncing, compression, and batch processing.
Features
Initial release of TableSync gem with documentation and CI configuration
This change introduces the TableSync gem, a tool for DB table synchronization between microservices using model events and RabbitMQ. It includes the initial gemspec, a comprehensive CHANGELOG documenting versions from 4.1.1 to 6.11.0, and updated README with installation and usage instructions. The project is configured with RSpec settings, Rubocop rules targeting Ruby 3.1, and a .gitignore that excludes logs and gem files. The Travis CI configuration is removed, indicating a shift away from that CI provider.
(repo-wide) · high confidence
Initial release of the TableSync gem for bidirectional database synchronization
This change introduces the TableSync library, enabling synchronization of database tables between different systems. It provides a publishing pipeline (supporting single, batch, and raw message formats with optional debouncing and compression) and a receiving pipeline with a DSL for configuring target models. The implementation includes ORM adapters for both ActiveRecord and Sequel, event validation, instrumentation via ActiveSupport::Notifications, and a plugin ecosystem for extensibility.
_lib/table\sync · high confidence
Behavioural changes
Major refactoring of the TableSync core library structure
The core library has been significantly restructured to support a modular architecture. The main entry point now loads a comprehensive set of internal components, including dedicated modules for ORM adapters (ActiveRecord and Sequel), setup configurations, naming resolvers, and instrumentation. New dependencies such as 'memery', 'self\_data', and 'rabbit\_messaging' have been introduced to handle messaging and data handling. The public API now exposes configuration options for publishing jobs, routing keys, and exchanges, while introducing a new 'sync' method that accepts options like 'debounce\_time' and 'compress' to configure synchronization behavior for specific object classes.
lib · high confidence
Test coverage
Initial test suite for TableSync core components
Added comprehensive RSpec tests covering the TableSync library's event handling, instrumentation, publishing (single, batch, and raw), receiving configuration, and ORM adapters (ActiveRecord and Sequel). These tests validate message construction, routing key resolution, debounce logic, attribute filtering, and notification payloads for both publish and receive flows.
spec · high confidence
Dependencies
Update Ruby requirement and runtime dependencies
The gem now requires Ruby 3.1.0 or higher (previously 2.3.8) and updates its runtime dependencies to include memery, rabbit\_messaging (\>= 1.8.0), rails, and self\_data. Development dependencies such as rspec, rubocop-config-umbrellio, and simplecov have been moved to the Gemfile, and the gemspec summary and description have been updated to reflect the product's purpose.
(dependencies) · high confidence
Housekeeping
Added log directory placeholder
A .keep file has been added to the log directory to ensure the directory is tracked by version control, preventing it from being ignored or removed by tools that clean up empty directories.
log · high confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 55 → 55 (-0.6)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 61 → 61 (+0.0)
- Architecture 96 → 96 (+0.0)
- Maturity 42 → 39 (-3.6)
- Readiness 64 → 64 (+0.0)
- Security 77 → 91 (+13.4)
Resolved (3)
- Duplicate intent between Event methods and Debounce helper methods. Event.upsert?() and Event.destroy?() seem to determine the type of operation for an event. Debounce.upsert_event?() and Debounce.destroy_event?() perform the same logical check but are located in a helper class. This duplication suggests that the Event class should be the single source of truth for determining the operation type, and the Debounce class should delegate to it or the Event class should expose these predicates directly.
- Inconsistent naming and scope for data retrieval operations. ORMAdapter.Base.find() suggests a generic lookup operation, while Receiving.Model.*.find_and_save() implies a specific transactional write-after-read pattern. If find() in the adapter is meant to be the generic lookup, it should not be mixed with the specific 'find_and_save' logic in the receiving models without clear distinction. Furthermore, 'find' is a very common name; if it behaves differently in different contexts (simple lookup vs. part of a save transaction), it should be named more descriptively (e.g., lookup_by_key vs. find_and_lock_for_update).
- Redundant entry points for publishing/syncing. TableSync.sync() appears to be a high-level convenience method that likely delegates to the Publishing classes. However, the Publishing.Single and Publishing.Batch classes expose their own publish_now/publish_later methods. This creates confusion about whether a user should call TableSync.sync() or instantiate a Publishing object and call publish_now. The intent (triggering a sync/publish) is identical, but the API surface offers two distinct paths with different signatures and object lifecycles.
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
umbrellio/table_sync was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 8 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 97ed98fcb3a146974aa0b1a80368c6e4b2da3124 — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-45ab2cab63de.