messaging

For testing purpose, I need to simulate client for generating 100,000 messages per second and send them to kafka topic. Is there any tool or way that can help me generate these random messages? There's a built-in tool for generating dummy load, located in bin/kafka-producer-perf-test.sh ( https://github.com/apache/kafka/blob/trunk/bin/kafka-producer-perf-test.sh ). You may refer to https://github.com/apache/kafka/blob/trunk/tools/src/main/java/org/apache/kafka/tools/ProducerPerformance.java#L106 to figure out how to use it. One usage example would be like that: bin/kafka-producer-perf-test.sh

RabbitMQ's Channel#basicConsume method gives us the following arguments: channel.basicConsume(queueName, autoAck, consumerTag, noLocal, exclusive, arguments, callback); Giving us the ability to tell RabbitMQ exactly which queue we want to consume from. But Channel#basicPublish has no such equivalency: channel.basicPublish(exchangeName, routingKey, mandatory, immediateFlag, basicProperties, messageAsBytes); Why can't I specify the queue to publish to here?!? How do I get a Channel publishing to, say, a queue named logging ? Thanks in advance! Basically queues can be binded to an exchange based

Ok here is an overview of what's going on: M <-- Message with unique id of 1234 | +-Start Queue | | | <-- Exchange /|\ / | \ / | \ <-- bind to multiple queues Q1 Q2 Q3 \ | / <-- start of the problem is here \ | / \ | / \|/ | Q4 <-- Queues 1,2 and 3 must finish first before Queue 4 can start | C <-- Consumer So I have an exchange that pushes to multiple queues, each queue has a task, once all tasks are completed, only then can Queue 4 start. So message with unique id of 1234 gets sent to the exchange, the exchange routes it to all the task queues ( Q1, Q2, Q3, etc... ), when all the tasks for

I'm looking to gain a better understanding of why it is recommended to never Publish() messages from a website using NServiceBus ( NServiceBus Documentation , scroll about two thirds of the way down). Doesn't it make semantic sense to Publish() events, and to Send() commands? If so, I think it makes sense that a web application can both Publish() and Send() :-) Also, given that using Publish() doesn't require the web application to know about the recipients of the messages (Send() requires the web application to have all recipient endpoints configured), it feels like Publish() is a better

I heard Amazon uses HTTP for its microservice based architecture. An alternative is to use a messaging system like RabbitMQ or Solace systems. I personally have experience with Solace based microservice architecture, but never with REST. Any idea what do various big league implementations like Amazon, Netflix, UK Gov etc use? Other aspect is, in microservices, following things are required (besides others): * Pattern matching * Async messaging.. receiving system may be down * Publish subscribe * Cache load event.. i.e. on start up, a service may need to load all data from a couple of other