kjnilsson

7 ms·

1.
by kjnilsson 4y ago
It depends on the current throughput of the system, how many queues a message is routed to, size of the message etc. But a mostly idle RabbitMQ cluster with fast disks should confirm a message published to a single quorum queue in a couple
2.
by kjnilsson 5y ago
Genuine question: what is it that you need from Kafka partitioning?
3.
by kjnilsson 5y ago
Log rentention is probably the main reason. Event sourcing typically would need some kind of snapshot to be calculated to replace the head of the log before it is deleted. If you had unbounded storage you could perhaps.
4.
by kjnilsson 5y ago
For me one of the nicest things is that you can have both "traditional" messaging _and_ streaming in the same system. Feeding messages published to exchanges into both queues (for processing) and streams for archiving, auditing an
5.
by kjnilsson 5y ago
AFAIK there is no proper standard streaming protocol which is why we went with a dedicated protocol that works really well with our approach to streams.
6.
by kjnilsson 5y ago
No they do not replicate like classic mirrored queues do. They are much more similar to quorum queues in that they only (asynchronously) replicate the delta after a disconnection. After all both streams and quorum queues use log replicatio
7.
by kjnilsson 6y ago
Proxying isn't hard to implement but in the erlang Raft implementation, Ra we decided only to do it when the client explicitly declares that it does not care about ordering. When proxying it is always possible that the client will find