Good questions. Happy to share any details that may be helpful. My concerns
could be off the mark. As I mentioned, I am still in the early stages of
grasping the implications of deciding to move toward Linux and the .NET
I have an existing MVC web client. It communicates with maybe a dozen
microservices via commands and event messages. Today, they are all on
Windows and use MSMQ for their transport. We also use the SignalR backplane
to push data to the browser.
From a business perspective, it would be ideal for the web client to be the
first end point moved to Linux/Core/NSB 7. I am accustomed to using MSMQ in
a fire and forget manner. I am also under the impression that some of that
behavior is the result of having a local instance of MSMQ on the web server
and distributed MSDTC transactions.
So, if I move the web client to Linux/ASP Core/NSB 7 and it needs to
send/receive commands or publish/subscribe to events that owned by one of
those 12 microservices…
- I can send commands to a Microservice over HTTP instead of MSMQ. No
fire and forget. No transactional consistency. Right?
- How does my web client receive information from the bus in this
scenario? This is the part of the process that is least clear to me right
- I believe I read that SignalR isn’t quite ready for ASP Core, yet.
But, I’m honestly not too concerned about this detail. If the web client
can receive the data via messages, I can find an appropriate mechanism for
pushing it to the browser with or without SignalR.
Hopefully that helps to clarify what I am contemplating. My intention is to
perform some experiments and POC’s before attempting to actually moving any
of our production systems to Linux/Core/NSB 7. I am just trying to pin down
the details that should be represented in those experiments and POC’s.