message-queue

I'm wondering if there is a tool or lib that can move messages between queues? Currently, i'm doing something like below public static void ProcessQueueMessage([QueueTrigger("myqueue-poison")] string message, TextWriter log) { CloudStorageAccount storageAccount = CloudStorageAccount.Parse(connString); CloudQueueClient queueClient = storageAccount.CreateCloudQueueClient(); CloudQueue queue = queueClient.GetQueueReference("myqueue"); queue.CreateIfNotExists(); var messageData = JsonConvert.SerializeObject(data, new JsonSerializerSettings { ContractResolver = new

I am currently struggle to find a solution for implement a specific kind of queue, which require the following traits: All queue must respect the order that job were added. The whole queue will have a concurrency of 1, which means that there will only be one job execute at a time per queue , not worker. There will be more than a few thousand queue like this. It need to be distributed and be able to scale (example if I add a worker) Basically it is a single process FIFO queue, and this is exactly what I want when tryout different message queue software like ActiveMQ or RabbitMQ, but as soon as

I'm having a bit of trouble with understanding JMS from a performance perspective. We have this very straightforward code in our application: QueueConnection connection = null; QueueSession session = null; QueueSender sender = null; TextMessage msg = null; try { // The JNDIHelper uses InitialContext to look up things QueueConnectionFactory qcf = JNDIHelper.lookupFactory(); Queue destQueue = JNDIHelper.lookupQueue(); // These objects are created for every message, which is quite slow connection = qcf.createQueueConnection(); session = connection.createQueueSession(false, Session.AUTO

I don't have much of a socket programming experience but I tried read a little about it. I am quite familiar with MDB and messaging queues. Someone has told me that queue(e.g. MDB) is "Not much more than a direct socket connection". Can someone compare these two for me. eeeeemph... this someone was very wrong. The two are incomparable, as they live in different layers. It's like saying that "a relational database is not much more than a file on a disk" or "a house is not much more than a brick". Messaging queue is a piece of software that glues senders and receivers so that they can

Closed . This question needs to be more focused. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it focuses on one problem only by editing this post . Closed 4 years ago . Can someone provide some rules of thumb regarding when to use Message Queueing and what practical real-world problems they are supposed to address? Thanks Asynchronous messaging allows systems to communicate in a disconnected manner. It is not necessary for both systems to be available simultaneously for work to get done. There are other benefits as well. Often

I have 3 node(nodes0,node1,node2) Kafka cluster(broker0, broker1, broker2) with replication factor 2 and Zookeeper(using zookeeper packaged with Kafka tar) running on a different node (node 4). I had started broker 0 after starting zookeper and then remaining nodes. It is seen in broker 0 logs that it is reading __consumer_offsets and seems they are stored on broker 0. Below are sample logs: Kafka Version: kafka_2.10-0.10.2.0 2017-06-30 10:50:47,381] INFO [GroupCoordinator 0]: Loading group metadata for console-consumer-85124 with generation 2 (kafka.coordinator.GroupCoordinator) [2017-06-30

Below is the desirable design of the queue with: P producer. The application that insert data X exchange. C1-C3 consumer. The applications that read from the queue Queue details: A. Is just like queue log, if there is no client binding then message will be discarded. B. This is a working queue. it will do something if there is criteria match. C. Also a working queue. it will transform the data A is optional, but B. C. will always in queue until some client process connect it. The problem is determine which type of exchange that i should use. is it a fanout, direct or topic ? because I wanted

When you store a message in a queue, isn't it more of meta data information so whoever pulls from the queue knows how to process the data? the actual information in the queue doesn't always hold all the information. Say you have an app like Twitter, whenever someone posts a message, you would still need to store the actual message text in the database correct? The queue would be more used to broadcast to other subscribers that a new message has arrived, and then those services could take further action. Or could you actually store the tweet text in the queue also? (or you COULD, but that would