decafsucks VS rom-sql

Compare decafsucks vs rom-sql and see what are their differences.

decafsucks

Rebuilding decafsucks.com as an OSS Hanami 2.0 example app (by decafsucks)
Ruby hanami-app Hanami dry-rb rom-rb
Source Code
Suggest alternative
Edit details

rom-sql

SQL support for rom-rb (by rom-rb)
Ruby SQL rom-rb Rubygem Postgresql MySQL Sqlite Sqlite3 MariaDB Mssql data-mapping Adapter Oracle
Source Code
rom-rb.org
Suggest alternative
Edit details
InfluxDB
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
Our great sponsors
decafsucks rom-sql
1 1
68 219
- 0.9%
5.1 5.9
12 days ago 3 months ago
Ruby Ruby
- MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

decafsucks

Posts with mentions or reviews of decafsucks. We have used some of these posts to build our list of alternatives and similar projects.
  • Ryan Bigg - Hanami 2.0 Thoughts
    1 project | /r/ruby | 28 Nov 2022
    In ordinary usage (i.e. outside the very simple rom setup in the getting started guide), I'd definitely recommend interacting with repos directly rather than the rom object itself. You can see this simple repo from my sample application (https://github.com/decafsucks/decafsucks/blob/8729deada9b6b6706b0e9893f535a198781ba3d0/slices/main/repos/cafe_repo.rb) as an example of an auto-registered repo. This can be resolved from my slice via `Main::Slice["cafe_repo"]` and is ready to use from there.

rom-sql

Posts with mentions or reviews of rom-sql. We have used some of these posts to build our list of alternatives and similar projects.
  • Sqlcomposer Early Preview Answering Questions
    1 project | /r/ruby | 8 Jan 2021
    Thank you, I really appreciate the thoughtful reply. Yeah, I'm beginning to understand it better, especially after seeing the latest bugfix. I'm curious to see how sql-composer will develop :)

What are some alternatives?

When comparing decafsucks and rom-sql you can also consider the following projects:

dry-cli - General purpose Command Line Interface (CLI) framework for Ruby

pgsync - Sync data from one Postgres database to another

dry-validation - Validation library with type-safe schemas and rules

Sequelize - Feature-rich ORM for modern Node.js and TypeScript, it supports PostgreSQL (with JSON and JSONB support), MySQL, MariaDB, SQLite, MS SQL Server, Snowflake, Oracle DB (v6), DB2 and DB2 for IBM i.

ROM - Data mapping and persistence toolkit for Ruby

vscode-sqltools - Database management for VSCode

dry-types - Flexible type system for Ruby with coercions and constraints

knex-tree - Query hierarchical data structures in sql with knex

dry-struct - Typed struct and value objects

sqlx - 🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite.

HeidiSQL - A lightweight client for managing MariaDB, MySQL, SQL Server, PostgreSQL, SQLite, Interbase and Firebird, written in Delphi

LINQ to DB - Linq to database provider.

decafsucks vs dry-cli rom-sql vs pgsync decafsucks vs dry-validation rom-sql vs Sequelize decafsucks vs ROM rom-sql vs vscode-sqltools decafsucks vs dry-types rom-sql vs knex-tree decafsucks vs dry-struct rom-sql vs sqlx rom-sql vs HeidiSQL rom-sql vs LINQ to DB