This is a difficult question to answer but briefly, it will depend on the services' design, state management of the system, concurrency-model, the domain and what the services will be doing. I presume they will have different behaviors with a mixture of cpu-bound, diskIO-bound, networkIO-bound, etc. That said, the embedded-mode broker is great for testing. If your system has distributed consumers and producers and HA requirements for the different pieces, it will not be the recommended option. Again, depends on your use cases.
On Wed, Aug 22, 2012 at 3:35 PM, Paddy Carman <paddy.car...@gmail.com>wrote: > Hi - > I'm trying to figure out the architecture for a large scale system that > I'm building that consists of hosting a number of services that would use a > pub/sub pattern. Could some please let me know the pros and cons of using > embedded broker Vs. standalone brokers especially in terms of scalability? > Thanks, > PC >
