Is this RabbitMQ / sockjs pub/sub connection setup a comet solution?
My company is attempting to set up a pub/sub connection using RabbitMQ and sockjs, on Windows servers. I have two questions:
How to implement a message queue over Redis?
Why Redis for queuing? I’m under the impression that Redis can make a good candidate for implementing a queueing system. Up until this point we’ve been using our MySQL database with polling, or RabbitMQ. With RabbitMQ we’ve had many problems – the client libraries are very poor and buggy and we’d like not to invest […]
Subscribing to a range of topics per instance of a service
If I have a system where my distributed service is sending live scores of 1000s of football games from some hypothetical event to millions of clients. The service subscribes to the games from a source service that publishes the scores. The source publish happens over the id of the game i.e. each game is published on a different topic that my service subscribes to.
Subscribing to a range of topics per instance of a service
If I have a system where my distributed service is sending live scores of 1000s of football games from some hypothetical event to millions of clients. The service subscribes to the games from a source service that publishes the scores. The source publish happens over the id of the game i.e. each game is published on a different topic that my service subscribes to.
Best way to notify the client in real time that their queue (e.g. SQS) job has finished?
Current Scenario
How is the publish-subscribe pattern different from gotos?
My understanding is that Goto statements are generally frowned upon. But the publish-subscribe pattern seems to be conceptually similar in that when a piece of code publishes a message, it performs a one-way transfer of control. The programmer may have no idea what parts of the program are subscribing to this message.
How is the publish-subscribe pattern different from gotos?
My understanding is that Goto statements are generally frowned upon. But the publish-subscribe pattern seems to be conceptually similar in that when a piece of code publishes a message, it performs a one-way transfer of control. The programmer may have no idea what parts of the program are subscribing to this message.
Design pattern for modifying state and notifying the other modifiers without a loop
The idea is that I have a set of properties that represent possible options in the app. These options can be modified through a variety of different ways, such as from the UI, remotely, third party, etc…
Design pattern for modifying state and notifying the other modifiers without a loop
The idea is that I have a set of properties that represent possible options in the app. These options can be modified through a variety of different ways, such as from the UI, remotely, third party, etc…
Design pattern for modifying state and notifying the other modifiers without a loop
The idea is that I have a set of properties that represent possible options in the app. These options can be modified through a variety of different ways, such as from the UI, remotely, third party, etc…