Hacker News: slotix

New comment by slotix in "Quack: The DuckDB Client-Server Protocol"

slotix — Tue, 12 May 2026 21:38:57 +0000

I read it less as "DuckDB wants to become Postgres" and more as DuckDB becoming an execution layer inside bigger workflows.

The engine is often not the painful part anymore. The pain is the stuff around it: live DBs, S3 paths, Parquet files, credentials, repeatable runs, exports, validation, and the moment a one-off script quietly becomes infrastructure.

Quack makes the remote/server part cleaner, but the bigger trend seems to be DuckDB becoming the SQL layer inside tools, not necessarily the final user-facing tool.

New comment by slotix in "Ask HN: What are you working on? (May 2026)"

slotix — Sun, 10 May 2026 23:33:06 +0000

We are working on DBConvert Streams:

https://streams.dbconvert.com

A self-hosted database IDE with built-in migration, CDC, and DuckDB-powered federated SQL.

Mostly trying to remove the annoying gap between "I can inspect this database" and "I can safely move/sync this data somewhere else".

Current focus: resumable large loads and cleaner initial-load-to-CDC handoff for Postgres/MySQL.

New comment by slotix in "Full-Text Search with DuckDB"

slotix — Thu, 30 Apr 2026 20:45:19 +0000

We wrapped exactly this into a GUI - attach MySQL and PostgreSQL, files/ s3 as sources, query them together with DuckDB. No imports. https://streams.dbconvert.com/cross-database-sql

Show HN: DBConvert Streams 2.0 – explore, migrate, sync. No pipeline glue

slotix — Tue, 14 Apr 2026 19:19:08 +0000

moving data between DBs still feels more manual than it should

most workflows look like: IDE -> export -> scripts -> pipeline -> CDC

so tried collapsing that into one tool:

query across PostgreSQL / MySQL / files use the query as a data source move it then turn on CDC

runs locally or via Docker

would love feedback, especially on: whether query-as-pipeline makes sense or if this just shifts complexity somewhere else

Comments URL: https://news.ycombinator.com/item?id=47770129

Points: 1

# Comments: 0

New comment by slotix in "Ask HN: What Are You Working On? (April 2026)"

slotix — Mon, 13 Apr 2026 14:36:43 +0000

Working on database tooling around data movement + CDC.

Trying to collapse what is usually:

SQL IDE -> export/scripts -> pipeline -> CDC -> back to SQL

into a single workflow instead of stitching 3–4 tools together.

Runs locally or via Docker, no Kafka / heavy setup.

https://streams.dbconvert.com/

Why database tools are split – and that's the real problem

slotix — Mon, 13 Apr 2026 14:25:48 +0000

Article URL: https://streams.dbconvert.com/blog/why-database-tools-are-split/

Comments URL: https://news.ycombinator.com/item?id=47752462

Points: 2

# Comments: 0

New comment by slotix in "Show HN: I got tired of juggling 4 tools for data work – built one instead"

slotix — Wed, 08 Apr 2026 16:23:32 +0000

Happy to answer questions about architecture, tradeoffs, or specific use cases.

Show HN: I got tired of juggling 4 tools for data work – built one instead

slotix — Wed, 08 Apr 2026 16:13:21 +0000

Every data workflow I touched had the same shape:

- explore schema in one tool - write and test queries in another - run the migration separately - set up CDC sync somewhere else

Each tool does its job fine. But the switching, glue scripts, and "wait, which connection config was this?" start to add up.

So I built DBConvert Streams 2.0, a self-hosted tool that keeps the whole workflow in one place:

explore -> verify -> migrate -> keep in sync

What it does:

- connect to PostgreSQL, MySQL, CSV/JSON/Parquet, S3-compatible storage - browse schemas and data - run SQL queries (including across different sources) - run one-time migrations or continuous CDC sync

The cross-source SQL part was the main thing I personally kept missing - usually this required exporting data or setting up extra tooling.

Tools like Debezium and Airbyte solve the pipeline side well, but I still ended up switching to other tools to explore and query data before or during the move.

Runs as a desktop app (Windows, macOS, Linux) or via Docker.

Comments URL: https://news.ycombinator.com/item?id=47692226

Points: 4

# Comments: 1

Show HN: Database Replication and Synchronization

slotix — Mon, 06 Feb 2023 11:32:07 +0000

Replicate data and synchronize changes from MySQL and PostgreSQL, enabling applications to respond to these changes in real-time with minimal latency.

Comments URL: https://news.ycombinator.com/item?id=34676014

Points: 2

# Comments: 0

New comment by slotix in "MySQL vs. PostgreSQL in 2023"

slotix — Mon, 06 Feb 2023 11:12:09 +0000

PostgreSQL and MySQL are both reliable, secure and scalable databases that have been around for years. They each have unique strengths and weaknesses, making one more suitable for specific needs. This article will compare them to aid in making an informed decision in 2023.