These are chat archives for NimbusAPI/Nimbus

14th
Dec 2015
Ashley Mannix
@KodrAus
Dec 14 2015 00:14
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
Damian Maclennan
@DamianMac
Dec 14 2015 00:14
Yeah it could well do, but CoreCLR is still changing so thats not a #1 priority
Ashley Mannix
@KodrAus
Dec 14 2015 00:16
That's what you have a community for ;)
Damian Maclennan
@DamianMac
Dec 14 2015 00:16
heh, it's more that it's effort that's better spent when coreclr settles down
but we're moving the sdk stuff out of the main assemblies so it's certainly more viable
I saw your comment on the issue though, it's still at the "hacking away at the shape of it" phase
are you based in the city ?
Andrew Harcourt
@uglybugger
Dec 14 2015 00:18
Hi all :)
Damian Maclennan
@DamianMac
Dec 14 2015 00:18
Hey
Andrew Harcourt
@uglybugger
Dec 14 2015 00:19
Just thought I'd drop in.
@DamianMac and I had a really productive day yesterday hacking on this stuff.
Damian Maclennan
@DamianMac
Dec 14 2015 00:19
death to BrokeredMessage
Andrew Harcourt
@uglybugger
Dec 14 2015 00:20
It's still at the "the toys are strewn all over the bedroom floor" stage of tidying the bedroom, but it's looking very promising.
BrokeredMessage and MessageLostLockException were the bane of my existence.
Horrible thing.
Ashley Mannix
@KodrAus
Dec 14 2015 00:20
Glad to hear it!
Damian Maclennan
@DamianMac
Dec 14 2015 00:21
What are you doing with Kafka @KodrAus ?
Andrew Harcourt
@uglybugger
Dec 14 2015 00:21
Taking back ownership of our concept of time has made things vastly more simple. I'm really looking forward to getting this stuff out the door.
Ashley Mannix
@KodrAus
Dec 14 2015 00:23
Right now just playing with it, writing a client for it in Rust, but would like to see how it fits as a more 'persistent' messaging channel
So do you guys have any ideas for nuget package design going forward?
Damian Maclennan
@DamianMac
Dec 14 2015 00:25
In what way ? I think they'll still be versioned archive files with manifests in them :)
Ashley Mannix
@KodrAus
Dec 14 2015 00:27
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?
Damian Maclennan
@DamianMac
Dec 14 2015 00:28
No I'd say you pick a transport. Nimbus.Transports.WindowsServiceBus , Nimbus.Transports.AzureServiceBus, Nimbus.Transports.Redis
it means a little more nuget hell though to get started, we were talking about a getting started script / page / app / something where you chose your options and it built a bootstrapper for you
Ashley Mannix
@KodrAus
Dec 14 2015 00:31
That'd be neat, package building / depending is not so bad with project.json though so having extra packages should be more managable
Damian Maclennan
@DamianMac
Dec 14 2015 00:32
we'll see how much project.json changes :)
Ashley Mannix
@KodrAus
Dec 14 2015 00:43
True. Well we're looking forward to what comes next! Thanks for diving back in :)
Damian Maclennan
@DamianMac
Dec 14 2015 00:43
:thumbsup:
Ashley Mannix
@KodrAus
Dec 14 2015 01:00
for nuget hell it might be worth taking a look at how Microsoft Orleans gets around it. They keep all nuspecs together and have a generic bat script that packs it all up. It's a bit ugly, but works
Andrew Harcourt
@uglybugger
Dec 14 2015 01:13
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?"
Ashley Mannix
@KodrAus
Dec 14 2015 01:31
You could include the getting started page that generates install-package commands from selections as a welcome page when installing the main Nimbus library?
But then you kind of open up a new set of problems for managing that list of packages... Maybe a convention Nimbus.{Logging|Transport|Whatever}.{Name}
Andrew Harcourt
@uglybugger
Dec 14 2015 01:41
@DamianMac was mulling over a little Angular app that would generate Install-Package commands and a C# bus configuration code snippet.
I'm starting to like this idea.
johncrn
@johncrn
Dec 14 2015 02:59
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.
Damian Maclennan
@DamianMac
Dec 14 2015 03:00
Thanks @johncrn .. that was one of the initial scenarios that we built it for :) :thumbsup:
johncrn
@johncrn
Dec 14 2015 03:00
Yep, worked like a charm and easy to onboard. Some of the other alternatives require too much ceremony.