--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-discuss+unsub...@googlegroups.com.
To post to this group, send email to masstransit-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/6b7d39e2-63fc-47ae-b8df-303249a2f9c6%40googlegroups.com.
Since you can have multiple receive endpoints on a single bus, there is really no reason to create more than one bus in a process. Particularly since it can eventually exhaust the usable connection limits of most brokers. Each connection is a bunch of threads and sockets under the hood, and that all adds up over time.
On Tue, Nov 29, 2016 at 7:14 AM, Alon Amsalem <alon.a...@gmail.com> wrote:
Also, I'd appreciate it if someone could mention what are the use cases that does require creating additional bus instance
On Tuesday, November 29, 2016 at 4:24:17 PM UTC+2, Alon Amsalem wrote:HiIs it considered a bad practice to create multiple buses in a single process?Is there a reason not to do that?Thank You,Alon Amsalem
--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-dis...@googlegroups.com.
To post to this group, send email to masstrans...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/6b7d39e2-63fc-47ae-b8df-303249a2f9c6%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-dis...@googlegroups.com.
To post to this group, send email to masstrans...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/CAHX4WYfuDLSyogq02eZBf3a%2B8eoHqa-b5TV0kwe0JH5dm4nnWA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
The only time I have had multiple buses is when I need to connect to multiple brokers. E.g. I have one RabbitMQ instance that does all the transactional data and sometime I need to shovel off messages to this subsystem that we keep on a different RabbitMQ instance/vhost. I would suggest the need for this is an edge case and most people won't require that system design.
On Tue, Nov 29, 2016 at 8:17 AM Chris Patterson <ch...@phatboyg.com> wrote:
Since you can have multiple receive endpoints on a single bus, there is really no reason to create more than one bus in a process. Particularly since it can eventually exhaust the usable connection limits of most brokers. Each connection is a bunch of threads and sockets under the hood, and that all adds up over time.
On Tue, Nov 29, 2016 at 7:14 AM, Alon Amsalem <alon.a...@gmail.com> wrote:
Also, I'd appreciate it if someone could mention what are the use cases that does require creating additional bus instance
On Tuesday, November 29, 2016 at 4:24:17 PM UTC+2, Alon Amsalem wrote:HiIs it considered a bad practice to create multiple buses in a single process?Is there a reason not to do that?Thank You,Alon Amsalem
--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-discuss+unsub...@googlegroups.com.
To post to this group, send email to masstransit-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/6b7d39e2-63fc-47ae-b8df-303249a2f9c6%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-discuss+unsub...@googlegroups.com.
To post to this group, send email to masstransit-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/CAHX4WYfuDLSyogq02eZBf3a%2B8eoHqa-b5TV0kwe0JH5dm4nnWA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
-----Travis
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-discuss+unsub...@googlegroups.com.
To post to this group, send email to masstransit-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/CAAqUTbkUEGXJycLu0SkC36kx%3DgUn6GP4nGOSDYgkbGiMDyE%3D7A%40mail.gmail.com.
Right, and you can have multiple hosts in a single bus now as well :)On Tue, Nov 29, 2016 at 8:24 AM, Travis Smith <tra...@legomaster.net> wrote:
The only time I have had multiple buses is when I need to connect to multiple brokers. E.g. I have one RabbitMQ instance that does all the transactional data and sometime I need to shovel off messages to this subsystem that we keep on a different RabbitMQ instance/vhost. I would suggest the need for this is an edge case and most people won't require that system design.
On Tue, Nov 29, 2016 at 8:17 AM Chris Patterson <ch...@phatboyg.com> wrote:
Since you can have multiple receive endpoints on a single bus, there is really no reason to create more than one bus in a process. Particularly since it can eventually exhaust the usable connection limits of most brokers. Each connection is a bunch of threads and sockets under the hood, and that all adds up over time.
On Tue, Nov 29, 2016 at 7:14 AM, Alon Amsalem <alon.a...@gmail.com> wrote:
Also, I'd appreciate it if someone could mention what are the use cases that does require creating additional bus instance
On Tuesday, November 29, 2016 at 4:24:17 PM UTC+2, Alon Amsalem wrote:HiIs it considered a bad practice to create multiple buses in a single process?Is there a reason not to do that?Thank You,Alon Amsalem
--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-dis...@googlegroups.com.
To post to this group, send email to masstrans...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/6b7d39e2-63fc-47ae-b8df-303249a2f9c6%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-dis...@googlegroups.com.
To post to this group, send email to masstrans...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/CAHX4WYfuDLSyogq02eZBf3a%2B8eoHqa-b5TV0kwe0JH5dm4nnWA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
---Travis
--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-dis...@googlegroups.com.
To post to this group, send email to masstrans...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/CAAqUTbkUEGXJycLu0SkC36kx%3DgUn6GP4nGOSDYgkbGiMDyE%3D7A%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-dis...@googlegroups.com.
To post to this group, send email to masstrans...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/CAHX4WYfZTN8%2BZvVAMhCQ3TK42YVg7QS3EgQkT31UH%3DjQyUOstA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Thanks a lot for the detailed response
Well, I'm not keeping up with all the features you ship Chris! So yeah, no reason to have multiple buses now.
On Tue, Nov 29, 2016 at 11:12 AM Chris Patterson <ch...@phatboyg.com> wrote:
Right, and you can have multiple hosts in a single bus now as well :)On Tue, Nov 29, 2016 at 8:24 AM, Travis Smith <tra...@legomaster.net> wrote:
The only time I have had multiple buses is when I need to connect to multiple brokers. E.g. I have one RabbitMQ instance that does all the transactional data and sometime I need to shovel off messages to this subsystem that we keep on a different RabbitMQ instance/vhost. I would suggest the need for this is an edge case and most people won't require that system design.
On Tue, Nov 29, 2016 at 8:17 AM Chris Patterson <ch...@phatboyg.com> wrote:
Since you can have multiple receive endpoints on a single bus, there is really no reason to create more than one bus in a process. Particularly since it can eventually exhaust the usable connection limits of most brokers. Each connection is a bunch of threads and sockets under the hood, and that all adds up over time.
On Tue, Nov 29, 2016 at 7:14 AM, Alon Amsalem <alon.a...@gmail.com> wrote:
Also, I'd appreciate it if someone could mention what are the use cases that does require creating additional bus instance
On Tuesday, November 29, 2016 at 4:24:17 PM UTC+2, Alon Amsalem wrote:HiIs it considered a bad practice to create multiple buses in a single process?Is there a reason not to do that?Thank You,Alon Amsalem
--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-discuss+unsub...@googlegroups.com.
To post to this group, send email to masstransit-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/6b7d39e2-63fc-47ae-b8df-303249a2f9c6%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-discuss+unsub...@googlegroups.com.
To post to this group, send email to masstransit-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/CAHX4WYfuDLSyogq02eZBf3a%2B8eoHqa-b5TV0kwe0JH5dm4nnWA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
---Travis
--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-discuss+unsub...@googlegroups.com.
To post to this group, send email to masstransit-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/CAAqUTbkUEGXJycLu0SkC36kx%3DgUn6GP4nGOSDYgkbGiMDyE%3D7A%40mail.gmail.com.--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-discuss+unsub...@googlegroups.com.
To post to this group, send email to masstransit-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/CAHX4WYfZTN8%2BZvVAMhCQ3TK42YVg7QS3EgQkT31UH%3DjQyUOstA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
-----Travis
You received this message because you are subscribed to a topic in the Google Groups "masstransit-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/masstransit-discuss/cPam7iHrwik/unsubscribe.
To unsubscribe from this group and all its topics, send an email to masstransit-discuss+unsub...@googlegroups.com.
To post to this group, send email to masstransit-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/CAAqUTbn%3DfSx7BZ0z4uXHKL-nKapS1804NRzTQB_iNYhHsQfdHw%40mail.gmail.com.