Hi, congrats on the show HN. Is it possible for you to Provide some comparison of this tool against other existing tools that can sync Postgres to Elastic or other third-party data providers.
I tried to give a detailed comparison with PGSync in another comment. But in a nutshell, PG to Elastic is just one use-case for PG-Capture. The goal for PG-Capture is to be a schema-based Change-Data-Capture utility for Postgres that lets you integrate into your existing stack.
It has no opinion on what you should use to capture low-level events (Debezium, WAL-Listener...) and what you should do with the resulting high-level events (indexation, caching, event bus..).
I am pitching it as a PG to Elastic tool simply because it is a widespread use-case that everyone understands.
It has no opinion on what you should use to capture low-level events (Debezium, WAL-Listener...) and what you should do with the resulting high-level events (indexation, caching, event bus..).
I am pitching it as a PG to Elastic tool simply because it is a widespread use-case that everyone understands.