News for hackers. Stuff that matters.
Re:Liftbridge: Lightweight, fault-tolerant message streams by tylertreat on Monday July 29, 2019 @09:36PM (#20561292)
Author here. Happy to answer any questions.
Re:Liftbridge: Lightweight, fault-tolerant message streams by softwarelimits on Tuesday July 30, 2019 @05:46AM (#20563352)
Hi, what are the message delivery guarantees with Liftbridge? I would like to replace a PostgreSQL based hand made queue system, but I need the transactional safety of a database - should I use Liftbridge?

Thank you very much for your attention!

Re:Liftbridge: Lightweight, fault-tolerant message streams by tylertreat on Tuesday July 30, 2019 @10:37AM (#20565177)
It has at-least-once delivery guarantees currently. I have plans for some lightweight transactional-style publishing with an idempotent producer though.
Re:Liftbridge: Lightweight, fault-tolerant message streams by networkimprov on Monday July 29, 2019 @10:04PM (#20561470)
What are the principal use cases?
Re:Liftbridge: Lightweight, fault-tolerant message streams by tylertreat on Tuesday July 30, 2019 @12:07AM (#20562068)
Basically the same types of uses cases as Kafka and similar systems: event sourcing, CQRS, stream processing (e.g. processing click stream events), data pipelines (e.g. log or metric aggregation used to feed multiple backends), or as a replicated transaction commit log (e.g. use it to create materialized views, populate caches or indexes, etc.). Log compaction means it can do this efficiently by just retaining the current state and discarding older transactions.

https://kafka.apache.org/uses