message-queue

问题 I am currently facing a problem for which I am pretty sure there is an official name, but I don't know what to search the web for. I hope that if I describe the problem and the solution I have in mind, somebody is able to tell me the name of the design pattern (if there is one that matches what I am going to describe). Basically, what I want to have is a job queue: I have multiple clients that create jobs (publishers), and a number of workers that process these jobs (consumers). Now I want to

问题 Sorry if my question is dumb, I'm new to MassTransit. My system consists of a server and multiple client devices. I'd like to send a message from the server to a specific client or to a group of clients. As far as I understand, IBusControl.Publish sends the message to all subscribers, and IBusControl.Send to the only one subscriber. How can I achieve this using MassTransit? My transports are RabbitMQ / Azure Service Bus. Thanks! 回答1: MassTransit implements standard messaging patterns, which

问题 When we configure the SSL on standalone ActiveMQ, we may need to provide the TrustStore,TrustStore Password, KeyStore and KeyStore password in client code to connect to the Active MQ over SSL protocol but in case of AmazonMQ, though they have provided SSL endpoint, but we can connect to it simply without providing the trust and key related values. Client code snippet for Simple ActiveMQ over SSL: ActiveMQSslConnectionFactory connFactory = new ActiveMQSslConnectionFactory("ssl://<someHost>

问题 When we configure the SSL on standalone ActiveMQ, we may need to provide the TrustStore,TrustStore Password, KeyStore and KeyStore password in client code to connect to the Active MQ over SSL protocol but in case of AmazonMQ, though they have provided SSL endpoint, but we can connect to it simply without providing the trust and key related values. Client code snippet for Simple ActiveMQ over SSL: ActiveMQSslConnectionFactory connFactory = new ActiveMQSslConnectionFactory("ssl://<someHost>

问题 It seems as though messages are not getting put onto the queue properly. I'm using Django with Celery and Kombu to make use of Django's own database as a Broker Backend. All I need is a very simple Pub/Sub setup. It will eventually deploy to Heroku, so I'm using foreman to run locally. Here is the relevant code and info: pip freeze Django==1.4.2 celery==3.0.15 django-celery==3.0.11 kombu==2.5.6 Procfile web: source bin/activate; python manage.py run_gunicorn -b 0.0.0.0:$PORT -w 4; python

问题 Most F# Message Passing examples I've seen so far are working with 2-4 message types, and are able to utilize pattern matching to direct each message to its proper handler function. For my application, I need hundreds of unique message types due to the different nature of their handling and required parameters. So far, each message type is its own record type with a marker interface attached, because including hundreds of types in a single discriminated union would not be very pretty - and

问题 Most F# Message Passing examples I've seen so far are working with 2-4 message types, and are able to utilize pattern matching to direct each message to its proper handler function. For my application, I need hundreds of unique message types due to the different nature of their handling and required parameters. So far, each message type is its own record type with a marker interface attached, because including hundreds of types in a single discriminated union would not be very pretty - and

问题 From the wouldn't-it-be-cool-if category of questions ... By "queue-like-thing" I mean supports the following operations: append(entry:Entry) - add entry to tail of queue take(): Entry - remove entry from head of queue and return it promote(entry_id) - move the entry one position closer to the head; the entry that currently occupies that position is moved in the old position demote(entry_id) - the opposite of promote(entry_id) Optional operations would be something like: promote(entry_id,

问题 From the wouldn't-it-be-cool-if category of questions ... By "queue-like-thing" I mean supports the following operations: append(entry:Entry) - add entry to tail of queue take(): Entry - remove entry from head of queue and return it promote(entry_id) - move the entry one position closer to the head; the entry that currently occupies that position is moved in the old position demote(entry_id) - the opposite of promote(entry_id) Optional operations would be something like: promote(entry_id,

问题 I am currently working on an online card game, similar to blackjack, which will consist of a series of tables where each table has a "dealer" and multiple human players. The dealer (a computer bot) is responsible for dealing and shuffling cards. The tables will be stored in a PostgreSQL database table and it will be possible for a human admin to add/remove/edit tables. The game will consist of a web front end and a REST/websocket API backend. I will probably use Kubernetes and Nginx as a load