News for hackers. Stuff that matters.
Re:Call me maybe: Elasticsearch 1.5.0 by lobster_johnson on Tuesday May 05, 2015 @07:15PM (#9495594)
The separation is nice, although I would counter that if your only primary data store is Postgres, and you want to go the logical decoding route, Postgres already has the queue: The decoded transaction log. There's no need for a queue on top of a queue. All you need now is a client that can process the log sequentially and emit each change to the appropriate data store.

Things like Kafka would be more appropriate if you have multiple producers that aren't all Postgres.

There are no comments on this comment yet.