bottledwater-pg

Event Sourcing [0] & CQRS [1] come to mind. I'm also a fan of Bottled Water [2] that turns Postgres ops into a stream of events that you can then push to other services. [0] https://martinfowler.com/eaaDev/EventSourcing.html [1] https://martinfowler.com/bliki/CQRS.html [2] https://github.com/confluentinc/bottledwater-pg

Short answer no, it doesn't (at least now, release 1 week ago :) ), but dismissing it only for that would be a superficial look. Most cases don't need those guarantees, i.e. you can tolerate a few lost messages. For example, you are implementing real time updates in your app using this. What's the probability of a network glitch happening at the same time as two users being logged in at the same time in one system where an event produced by one needs to be synced to the other, even more, say he lost that event, is it that critical considering he will soon move to another screen and reload the data entirely? From rabbitmq point of view, db&bridge are producers. You are really asking here, does the "producer" guarantee delivery? To do that, it means the producer needs to become himself a "queue" system in case he fails to communicate with

This tool enables a decoupled architecture. A simple example is sending emails when a user signs up. Instead of having explicit code in your signup function that does the work (and slows down your response), you just have to worry about inserting the row into the database. After this, a database trigger will generate an event which gets sent to RabbitMQ. From there, you can have multiple consumers reacting to that event (email, sms, log, cache). Those consumers tend to be very short, self contained scripts. A more complex example is if you pair pg-amqp-bridge and the Web STOMP plugin for RabbitMQ, you can enable flexible and robust real time updates with almost zero code for your frontend. The larger goal is to enable the development of backends around PostgREST [1] / subZero [2] philosophy. Check out the PostgREST Starter Kit [3] to see

Related: - https://github.com/zendesk/maxwell - https://github.com/confluentinc/bottledwater-pg

along the same lines https://github.com/confluentinc/bottledwater-pg

Hmm, interesting. Sounds like a problem with a Postgres, not Citus, but it still sounds like a disadvantage compared to competing products (RethinkDB also comes to mind). I haven't implemented anything for that before personally; would a tool like Bottled Water [0] be helpful for this usecase? [0] https://github.com/confluentinc/bottledwater-pg

There are actually a few strong solutions out there for Mysql, most starting with change data capture like: https://github.com/shyiko/mysql-binlog-connector-java (I link that one in particular because he links to alternatives right in his readme!) Pgsql is a bit harder, but if I needed to start somewhere it would be with: https://github.com/debezium/debezium or https://github.com/confluentinc/bottledwater-pg These are the start of pretty sophisticated solutions where you need super real-time elasticsearch indexes and can bring up infra like Kafka. For many applications, queueing an update when something hits your ORM to update, with the hourly/daily refresh is pretty satisfactory.