At its core it’s an elixir server which listens to Postgres’s built-in replication functionality, converts the byte stream to JSON, then blasts it out over websockets.
It’s working in production at a few companies now. My next goal is to build connectors to other systems like Kafka, SQS etc
FWIW, the README.md says "the Phoenix server listens to PostgreSQL's replication functionality (streaming WAL)" - that makes it sound like you're actually parsing the WAL itself. But you seem to be looking at the already decoded data (using postgres' logical decoding). That's the right thing to do, please don't get me wrong. Just suggesting to clarify.
At its core it’s an elixir server which listens to Postgres’s built-in replication functionality, converts the byte stream to JSON, then blasts it out over websockets.
It’s working in production at a few companies now. My next goal is to build connectors to other systems like Kafka, SQS etc