Fancy stream processing made operationally mundane
- message-queue
- stream-processing
- streaming-data
- message-bus
87,075 visible repositories in the index
1–15 of 15 · Most stars
Fancy stream processing made operationally mundane
Data pipelines for cloud config and security data. Build cloud asset inventory, CSPM, FinOps, and vulnerability management solutions. Extract from AWS, Azure, GCP, and 70+ cloud and SaaS sources.
Privacy and Security focused Segment-alternative, in Golang and React
RedisShake is a Valkey/Redis data processing and migration tool.
Apache DevLake is an open-source dev data platform to ingest, analyze, and visualize the fragmented data from DevOps tools, extracting insights for engineering excellence, developer experience, and community growth.
sq data wrangler
Connect your company's data, let an agent draft an ontology over it, and load it into HelixDB as one graph you can explore and ask questions of. Hosted at foundry.helix-db.com, or run it on your own machine.
Build data pipelines with SQL and Python, ingest data from different sources, add quality checks, and build end-to-end flows.
OLake - Fastest Databases, Kafka & S3 Replication to Apache Iceberg with Table optimization (Called OLake Fusion). ⚡ Efficient, quick and scalable data ingestion for real-time analytics. Supported sources : Postgres, MongoDB, MySQL, Oracle, MSSql, DB2, Kafka, S3.
Distributed Data Transfer Service for MySQL
This repo maintains DM (a data migration platform) and TiCDC (change data capture for TiDB)
The data platform for manufacturing
A fast to develop, fast to run, Go based toolkit for ETL and feature extraction on Hadoop.
🇪🇺 Warehouse-native Analytics compatible with Google Analytics and Matomo tracking protocols. Ingest into ClickHouse, BigQuery or CSV/Parquet on S3/GCS/local fs while maintaining complete control over your data.
Go tool + library that publishes GIS vector data to GeoServer via PostGIS — walks a directory of shapefile / GeoJSON / GeoPackage / KML, loads each into PostGIS via GDAL/OGR, then registers the resulting tables as GeoServer feature types. Idempotent. Tested on GeoServer 2.27 LTS + 2.28 stable.