1,864 karma · joined January 6, 2011
This is the castle of my master, Guy de Lombard.
I'd be curious to know, though, and without being too critical, how this change affects his kids? Did they have to change schools? Leave friends and be further away from family? I ask mainly because as a kid I was often a victim of my mother's fickleness, and as a parent it has been a goal of mine to give my kids the stability I didn't have. Again, not a judgement here, just interested in hearing about that aspect of this endeavor.
"I don't want to sell anything, buy anything, or process anything as a career. I don't want to sell anything bought or processed, or buy anything sold or processed, or process anything sold, bought, or processed, or repair anything sold, bought, or processed. You know, as a career, I don't want to do that."
A Lisp would be nasty, too. "... Close paren. Close paren. Close paren. Close paren. ..."
That said, for a larger deployment you'd still probably want to run the lookupd as well, at which point, at least for a typical architecture, running nsqd standalone is probably fine. Embedding is darn handy for testing, though.
It's super easy to run. A few command line params, if that, and I've got a local nsqd running that I can develop and test against. Great for those offline coding sessions on BART.
The tools it ships with are very handy, specifically to_nsq and nsq_tail. Again, both make developing stuff really easy because I can get stuff in and out with fast, native command line tools or http. In fact, when I was first playing around I built an entire prototype based on a few simple shell scripts and the provided tools, just to see what would happen.
The nsqadmin and nsq_stat tools give you a lot of visibility into what your producers and consumers are doing, how well things are performing, who is connected to what, etc. And again, part of the distribution and very easy to run locally.
The Go producer and consumer API is clean and easy to build around, pretty well documented with a lot of examples in the NSQ apps themselves.
So far very stable. I haven't seen any crashes on the server or producer/consumer side.
Helpful and friendly people on a low noise freenode channel.