Sandglass
Infrastructure
message queue
SHOW HN2017
188points
68comments
#184of 2,242 in 2017
Top 9%of 2017 by points
How HN took it
MixedNo clear lean
4 positive, 9 neutral or asking, 0 mixed, 10 critical, out of 23 comments about the project. Thread score -0.17.
Docs: 2 for, 5 againstIdea: 1 for, 2 againstExecution: 0 for, 3 againstDesign: 1 for, 0 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Interesting and promising project
From 3 comments
This looks promising. I'm currently dealing with a queuing-related issue. I have a series of tasks running across servers that consume from a queue and run a task. Often, these…
adrinavarro on HNthis is awesome, is it meant to replace kafka ?
yassinebenyahia on HNLooking good. Question is how is it going to convince people to move over from Kafka.
ninjamayo on HN
Objections
Exactly-once delivery and time ordering in a highly available queue is a suspicious trade-off
From 2 comments
It triggers my eyebrow when a highly available message queue offers either exactly-once delivery or reliable time sorting. I'm not saying I wouldn't give this project a closer…
menacingly on HNUsually 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…
menacingly on HN
Product description is buzzword-heavy and unclear about the problem solved
From 2 comments
These buzzword product descriptions are terrible. Documentation should say first, what does this piece of code do and when should I use it. The actual rationale for this project…
eddd on HNI think that product pages should clearly communicate what the product is to the intended audience. These are 100% buzzwords, so the message I get is, "you will need to spend…
falsedan on HN
Project is immature with a single contributor
From 1 comment
I have no opinion about each of these projects, but his caught my eye: > Well document set of edge cases / compromises where applicable and a high degree of observability. Well…
moreless on HN
Requests
Jepsen-style testing of partitions and node failures
From 2 comments
Aphyr's Jepsen or it didn't happen :-)
jwr on HNFaktory is CouchDB, Machinery is Redis/Memcache/MongoDB, Sandglass is a custom Raft on top of RocksDB… I'd love to see comparative stress tests, Jepsen-like, to assess the…
espadrine on HN
Clearer documentation of compromises and use cases
From 2 comments
These buzzword product descriptions are terrible. Documentation should say first, what does this piece of code do and when should I use it. The actual rationale for this project…
eddd on HN> Question is how is it going to convince people to move over from Kafka That's a bit unfair given that the project didn't mention Kafka in it's README and different products…
buro9 on HN
Questions
Does it replace Kafka?
From 3 comments
this is awesome, is it meant to replace kafka ?
yassinebenyahia on HNWhy does everyone keep alluding to this replacing kafka? If anything this is more similar to RabbitMQ.
lloydatkinson on HNLooking good. Question is how is it going to convince people to move over from Kafka.
ninjamayo on HN
How does it compare to NATS?
From 1 comment
How does this compare with NATS?
velodrome on HN
Does it support replay from offset or time?
From 1 comment
I hadn't heard of Pulsar before but just checked it out as we use Kafka. Does it support replaying messages from an offset (or even better, a time) like Kafka does? I looked at…
aphistic on HN
Alternatives named
RabbitMQ
From 2 comments
It triggers my eyebrow when a highly available message queue offers either exactly-once delivery or reliable time sorting. I'm not saying I wouldn't give this project a closer…
menacingly on HNWhy does everyone keep alluding to this replacing kafka? If anything this is more similar to RabbitMQ.
lloydatkinson on HN
Kafka
From 2 comments
Kafka perhaps?
dkersten on HNHaven't looked but the ordering has to be per partition. > something else https://www.confluent.io/blog/exactly-once-semantics-are-possible-heres-how-apache-kafka-does-it/
eternalban on HN
Redis streams
From 2 comments
Perhaps redis streams http://antirez.com/news/114
markbnj on HNI would think the imminent Redis streams data type would provide this better. It is battle-tested and allows great customisation to a range of use cases.
nicois on HN
Faktory
From 1 comment
Seems similar to faktory ? https://github.com/contribsys/faktory
agnivade on HN
NATS Streaming
From 1 comment
Note: There is NATS streaming [1] which implements persistence and redelivery. [1]: http://nats.io/documentation/streaming/nats-streaming-intro/ [2]:…
piotrkubisa on HN