Show HN: Sandglass – Distributed, scalable, persistent time-sorted message queue

Re:Show HN: Sandglass – Distributed, scalable, persistent ti... by meebs on Monday December 11, 2017 @11:14AM (#15897951)

Hey, what would "something else" be in this scenario?

[ Parent | on HN ]

Re:Show HN: Sandglass – Distributed, scalable, persistent ti... by menacingly on Monday December 11, 2017 @01:22PM (#15899045)

Usually it would advertise "at-least-once" somewhere prominently, like SQS, NSQ, etc.

It's really hard to be extremely available and to also guarantee there won't be dupes or out-of-order messages. Like databases, someone saying they offer both is usually hiding a trade-off.

EDIT: I think here "really hard" is a polite way of saying "impossible"

[ Parent | on HN ]

Re:Show HN: Sandglass – Distributed, scalable, persistent ti... by markbnj on Monday December 11, 2017 @02:06PM (#15899394)

Perhaps redis streams http://antirez.com/news/114

[ Parent | on HN ]

Re:Show HN: Sandglass – Distributed, scalable, persistent ti... by dkersten on Monday December 11, 2017 @12:45PM (#15898690)

Kafka perhaps?

[ Parent | on HN ]