Hi all! Great to hear dev is picking up again. We've used Nimus since you guys demo-ed it at the Brisbane meetup. Took a look at local messaging a while ago, couldn't work it out. Would like to see what's possible with a new decoupled messaging design. It would open the doors for CoreCLR support too
I mean currently there's the contract bits, infrastructure bits and the library, and modules for logging, IoC etc. I'm guessing transports would now go the way of other implementations, but would one be included by default? Like ConsoleLogger for logging?
Packing it isn't at all painful - that's actually pretty trivial. It's more a question of "How do I pick and choose the Nimbus components I want without running a boatload of Install-Package commands?"
Hi guys, great to hear you're moving forward on this one. Nimbus was very handy when I had to quickly roll out an internal tool that needed a request/response pattern getting to a fire walled system. Redis support definitely a good way to move things forward.