MassTransit.Http for inter-process messaging?

[Zsolt Soczo]

Hello,

  I could not find any documentation for MassTransit.Http. I'm interested in this because I have to establish messaging within a computer but between multiple processes without any outside dependencies, like RabbitMQ. This library seems to be good for this purpose. Am I right?

Can anyone point to any documentation for this facility? The only usage I've seen is in the unit tests.

Thanks,

Zsolt

[Chris Patterson]

If you just need HTTP/RPC, I'm not sure MT is the right choice for you. There are many other libraries that do that well, with good documentation.

MassTransit is meant for message-based architectures, with durable asynchronous processing, and shouldn't be used for a general HTTP client/service application. The HTTP support is there for interoperating with HTTP endpoints, within a message-based applicaiton.

--
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/3a6b31d7-2bf3-48fa-88ba-cb5ae64f8051%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Zsolt Soczo]

Thanks for your answer. My question was not precise.

So, we want to communicate in async manner using events in a load balanced environment between the LB nodes. For this purpose we tested MT with RabbitMQ, and it worked excellently. However, we have to scale down the system for customers who want single machine deployment. This is the scenario for which we need a transport layer which does not use external store like RabbitMQ to avoid deploying it to hundreds of machines. We don't need persistence in this scenario. The InMemory transport is not appropriate for us because we have to send events between processes on the same machine. Some shared memory or other IPC based transport would suffice. I thought MassTransit.Http is such a transport layer, capable of IPC within a machine.

Thanks,

Zsolt

2018. augusztus 1., szerda 14:32:41 UTC+2 időpontban Chris Patterson a következőt írta:

If you just need HTTP/RPC, I'm not sure MT is the right choice for you. There are many other libraries that do that well, with good documentation.

MassTransit is meant for message-based architectures, with durable asynchronous processing, and shouldn't be used for a general HTTP client/service application. The HTTP support is there for interoperating with HTTP endpoints, within a message-based applicaiton.

On Wed, Aug 1, 2018 at 5:51 AM, Zsolt Soczo <zsolt...@gmail.com> wrote:

Hello,

  I could not find any documentation for MassTransit.Http. I'm interested in this because I have to establish messaging within a computer but between multiple processes without any outside dependencies, like RabbitMQ. This library seems to be good for this purpose. Am I right?

Can anyone point to any documentation for this facility? The only usage I've seen is in the unit tests.

Thanks,

Zsolt

--
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 masstrans...@googlegroups.com.

[Chris Patterson]

It hasn't been tested in that scenario, at all. For a single box, just install a single-node RMQ on that machine. The process is fairly lightweight.

On Wed, Aug 1, 2018 at 9:55 AM, Zsolt Soczo <zsolt...@gmail.com> wrote:

Thanks for your answer. My question was not precise.

So, we want to communicate in async manner using events in a load balanced environment between the LB nodes. For this purpose we tested MT with RabbitMQ, and it worked excellently. However, we have to scale down the system for customers who want single machine deployment. This is the scenario for which we need a transport layer which does not use external store like RabbitMQ to avoid deploying it to hundreds of machines. We don't need persistence in this scenario. The InMemory transport is not appropriate for us because we have to send events between processes on the same machine. Some shared memory or other IPC based transport would suffice. I thought MassTransit.Http is such a transport layer, capable of IPC within a machine.

Thanks,

Zsolt

2018. augusztus 1., szerda 14:32:41 UTC+2 időpontban Chris Patterson a következőt írta:

If you just need HTTP/RPC, I'm not sure MT is the right choice for you. There are many other libraries that do that well, with good documentation.

MassTransit is meant for message-based architectures, with durable asynchronous processing, and shouldn't be used for a general HTTP client/service application. The HTTP support is there for interoperating with HTTP endpoints, within a message-based applicaiton.

On Wed, Aug 1, 2018 at 5:51 AM, Zsolt Soczo <zsolt...@gmail.com> wrote:

Hello,

  I could not find any documentation for MassTransit.Http. I'm interested in this because I have to establish messaging within a computer but between multiple processes without any outside dependencies, like RabbitMQ. This library seems to be good for this purpose. Am I right?

Can anyone point to any documentation for this facility? The only usage I've seen is in the unit tests.

Thanks,

Zsolt

--
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+unsubscribe...@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/3a6b31d7-2bf3-48fa-88ba-cb5ae64f8051%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/7ae43679-4699-4152-a788-a1c5ba2b7e98%40googlegroups.com.