- Its great we support queues approach.
- Documentation should guide user how to implement basic event.
- RabbitMq documentation, need a refactor to match Kafka.
- Default search in preview build doesn't work.
- With some knowledge about queues, users should undertand what documentation is pointing at.
- Kafka got whole flow step by step documented, but in RabbitMq user need to think with queue is responsible to work with message as queues are in other place in documentation.
- Generaly yes, but RabbitMq docs missing description of publish compared to Kafka examples.
- Kafka documentation have nested properties with + sign to open and check with is nice, RabbitMq have description of "array" with 1 item with is weak when comparing to kafka.
Seems like documentation suggest host and port on with RabbitMq should be connected to operates on queues
Kafka documentation got even more informations about server connection.
- In Kafka documentation, ther is a clear message we have publisher, and one line lower information about consumer, and what it does. In RabbitMq user need to know he should look into queue for consumer becouse he is missing any redirect button or information from exchange with publish event.
- (RabbitMq) Its possible to scroll and navigate from exchange with publish event to queue with consume it, but maybe there could writed as 1 process, ex: description of exchange, example payload, how to pushlish it, and then queue with consumer it. Kafka documentation, have 1 process - Topic, how to prepare message, what can be published and how to subscribe this topic.
Maybe it would be cool to have possibility to publish example event and see how its consumed?
Analytics exchange one of properties have example and value same with is a bit weird, and example for subject/data is "array of 1 item" without example.