message-queue

Queues against Tables in messaging systems [closed]

孤街醉人 提交于 2019-11-29 20:30:45
I've been experiencing the good and the bad sides of messaging systems in real production environments , and I must admit that a well organized table or schema of tables simply beats every time any other form of messaging queue, because: Data are permanently stored on a table. I've seen so many java (jms) applications that lose or vanish messages on their way for uncaught exceptions or other bugs. Queues tend to fill up. Db storage is virtually infinite, instead. Tables are easily accessible, while you have to use esotic instruments to read from a queue. What's your opinion on each approach?

Is Apache Kafka appropriate for use as an unordered task queue?

泪湿孤枕 提交于 2019-11-29 20:20:34
Kafka splits incoming messages up into partitions, according to the partition assigned by the producer. Messages from partitions then get consumed by consumers in different consumer groups. This architecture makes me wary of using Kafka as a work/task queue, because I have to specify the partition at time of production, which indirectly limits which consumers can work on it because a partition is sent to only one consumer in a consumer group. I would rather not specify the partition ahead of time, so that whichever consumer is available to take that task can do so. Is there a way to structure

Inter-process event emitter for Node.js?

有些话、适合烂在心里 提交于 2019-11-29 19:53:58
问题 At the moment, I am using EventEmitter2 as a message bus inside my application, and I really like it. Anyway, now I need a message bus which does not only work in-process, but also inter-process. My ideal candidate would … … be API-compatible to EventEmitter2 (a "drop-in replacement"), … work without a dedicated server or external service (such as a database, a message queue, …), only using OS resources, … be written in pure JavaScript, … run in-memory, so it does not require persistence.

Message Queues in Ruby on Rails

六眼飞鱼酱① 提交于 2019-11-29 19:37:41
What message queues are people using for their Rails apps and what was the driving force behind the decision to choose it. Does the latest Twitter publicity over their in house queue Starling falling down affect any existing design decisions. I am working on an app that will need a message queue to process some background tasks, I haven't done much of this, and most of the stuff I have seen in the past has been about Starling and Workling, and to be honest the application is not very big and this solution would probably suffice, but I'd love to get experience integrating the best solution

GetAsyncKeyState() causes anti-virus program to flag as keylogger

不问归期 提交于 2019-11-29 17:31:28
I have been building a very small game in the Windows API, and in the main message loop I use GetAsyncKeyState() to test if a user is pressing the arrow buttons. I use this instead of WM_KEYDOWN because with WM_KEYDOWN there is an initial pause after the first press, and I don't want to modify a user's settings. My antivirus program flags the game as a keylogger program, is there an alternative way about this? How is the anti-virus program supposed to guess that you are not using GetAsyncKeyState() to spy on the keyboard and log keys? You tell it of course, make an exclusion. If you're worried

To fork or not to fork?

孤街浪徒 提交于 2019-11-29 13:51:37
I am re-developing a system that will send messages via http to one of a number of suppliers. The original is perl scripts and it's likely that the re-development will also use perl. In the old system, there were a number of perl scripts all running at the same time, five for each supplier. When a message was put into the database, a random thread number (1-5) and the supplier was chosen to ensure that no message was processed twice while avoiding having to lock the table/row. Additionally there was a "Fair Queue Position" field in the database to ensure that a large message send didn't delay

Not able to Stop MQueue listener

被刻印的时光 ゝ 提交于 2019-11-29 12:53:46
I have the following configuration for my MQueue: <jms:listener-container container-type="default" connection-factory="cachedConnectionFactory" acknowledge="auto"> <jms:listener id="myListenerId" destination="myDestination" ref="myListener" method="onMessage" /> </jms:listener-container> When I try to stop the reception of JMS messages, I write the following code jmsManagement = myProject.instance.getContext().getBean('myListenerId',Lifecycle.class); jmsManagement.stop(); PS : When I stop() my listener, the isRunning() return False, but I still get messages through the MQueue... the onMessage

How to receive dynamic length data from a message queue?

a 夏天 提交于 2019-11-29 10:28:38
问题 I have to send and receive dynamic data using a SysV message queue for a university project. The length of the data is transmitted in a separate message, size is therefor already known. And this is how I try to receive the data. I have to admit that I'm not a C++ specialist, especially when it comes to memory allocation. struct { long mtype; char *mdata; } msg; msg.mdata = (char *)malloc(size * sizeof(char)); msgrcv(MSGQ_ID, &msg, size, MSG_ID, 0); The problem seems to be the malloc call, but

Node JS message queue on Heroku

ε祈祈猫儿з 提交于 2019-11-29 07:17:32
I need to move my Node JS server running on Heroku to a message queue architecture. Currently, the server receives a HTTP request, does some processing, and responds. The problem is that the processing takes some time, especially when there are lots of requests. This lengthy processing time causes the server to timeout, overload, and crash! My reading tells me a need a background worker to do the processing. I have zero experience with message queues and background workers and I'm looking for a very simple example to get started. Can anyone suggest a simple, understandable module or example to

Multithreaded single-reader single-writer fifo queue

家住魔仙堡 提交于 2019-11-29 03:22:05
问题 I need a queue for passing messages from one thread (A) to another (B), however ive not been able to find one that really does what I want, since they generally allow adding an item to fail, a case which in my situation is pretty much fatal since the message needs to be processed, and the thread really cant stop and wait for spare room. Only thread A adds items, and only thread B reads them Thread A must never block, however thread B is not performance critical, so it can Adding items must