soda-sql VS trino_data_mesh

Compare soda-sql vs trino_data_mesh and see what are their differences.

trino_data_mesh

Proof of concept on how to gain insights with Trino across different databases from a distributed data mesh (by findinpath)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
soda-sql trino_data_mesh
25 1
50 8
- -
8.2 1.8
over 1 year ago almost 3 years ago
Python
Apache License 2.0 -
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.

soda-sql

Posts with mentions or reviews of soda-sql. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-03-18.

trino_data_mesh

Posts with mentions or reviews of trino_data_mesh. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-07-29.
  • What even is data mesh
    2 projects | news.ycombinator.com | 29 Jul 2021
    Not central to the main ideas of this article, but if you want to have a data mesh that is self-service, why force folks to use a particular storage medium like a data warehouse? That still requires centralization of the data.

    Why not instead have a tool like Trino (https://trino.io) that allows you to let different domains use whatever datastore they happen to use. You still would need to enforce schema, but this can be done in tools like schema registry as mentioned in the article along with a data cataloging tool.

    These tools facilitate the distributed nature of the problem nicely and encourage healthy standards to be discussed and the formalized in schema definitions and catalogs that remove the ambiguity of discourse and documentation.

    Nice example is laid out in this repo of how Trino can accomplish data mesh principles 1 and 3 (https://github.com/findinpath/trino_data_mesh).

What are some alternatives?

When comparing soda-sql and trino_data_mesh you can also consider the following projects:

deequ - Deequ is a library built on top of Apache Spark for defining "unit tests for data", which measure data quality in large datasets.

lightdash - Open source BI for teams that move fast ⚑️

pandera - A light-weight, flexible, and expressive statistical data testing library

Trino - Official repository of Trino, the distributed SQL query engine for big data, formerly known as PrestoSQL (https://trino.io)

sqlfluff - A modular SQL linter and auto-formatter with support for multiple dialects and templated code.

dbt-customer-journey-analysis - Using DBT for Customer Journey Analysis on RudderStack - an open-source, warehouse-first customer data pipeline and Segment alternative.

dbt-sessionization - Using DBT for Creating Session Abstractions on RudderStack - an open-source, warehouse-first customer data pipeline and Segment alternative.

dbt-spotify-analytics - Containerized end-to-end analytics of Spotify data using Python, dbt, Postgres, and Metabase

re_data - re_data - fix data issues before your users & CEO would discover them 😊

spark-fast-tests - Apache Spark testing helpers (dependency free & works with Scalatest, uTest, and MUnit)

Prefect - The easiest way to build, run, and monitor data pipelines at scale.