I do, but only in smaller side projects and I'd love to hear from someone who has experience with both in larger settings. Although they work very differently, the query language (Cypher vs. Datalog) have a very similar feel to them. When I tried them it seemed that Datomic would be the more flexible of the 2 (eg. for use cases where you'd want a bit of relational and a bit of graph support), and that Neo4j you'd end up with PostgreSQL next to Neo4j in many practical applications. I have to say though that the query/visualization UI that Neo4j provides is nice and helps with making sure your data is indeed stored in the way you want.
We recently did this, and it's not that big of a deal. In our case, a 30-line sql script did the job (mostly related to renaming fk fields in other tables, and re-creating indexes and constraints). More than happy to share, although it's very specific to our app of course.
I'd be really interested to hear about the actual migration. That's what I thought this article was going to be about, instead of just how to use the feature.
Great! Love the product btw, I really think it solves a clear pain point. One feature request: give the option to send checks (through the API preferably) vs. an ACH. An ACH is not always feasible.
Thanks! We've definitely explored this option. Part of being an open company is that we publicly discuss our roadmap, I'd love it if you just +1'ed via our github tracker so you can get updated about our progress in that direction.
If we have enough interest on this feature, we'll reopen the issue and track its progress publicly:
This is probably not the site you are looking for!
You attempted to reach blog.balancedpayments.com, but instead you actually reached a server identifying itself as secure.static.tumblr.com. This may be caused by a misconfiguration on the server or by something more serious. An attacker on your network could be trying to get you to visit a fake (and potentially harmful) version of blog.balancedpayments.com.
You should not proceed, especially if you have never seen this warning before for this site.
Did you try scrolling using Safari instead of Chrome/Firefox? With the Retina display, scrolling is significantly smoother on Safari (aka it's not smooth on a 15" Retina on Chrome either).
While I'm not a Chef fanboy, far from it, some of these comments are just not true.
"and does stuff like execute apt for each desired package on each node on each run". No you just need to set it up correctly so that it keeps the timestamp of the latest apt-get update, and does not refresh it within the next x hours.
ZeroMQ is a library, it is embedded in the application code and can support a peer-to-peer messaging topology. It also has support for Broker patterns but you have to develop the Broker application yourself; you could build a solution such as this one using it, but the zmq library itself really handles lower-level concerns with a high degree of flexibility but no out-of-the-box functionality. zmq can be thought of as something as simple as an improved socket library but with support for async, storing & high-water marks when there are no attached consumers, various distribution strategies, queues and lots more.
Right, I guess my question more specifically is: ZeroMQ allows you to built applications like this in (seemingly) just a few lines of code. Did you guys consider building it on top of ZeroMQ, and if so, what made your decide to not use it? Nothing against what you've built btw, it looks great, but am just curious
The truth is we wanted to use ZeroMQ initially. It would have been really awesome to have all that flexibility on the client side.
The ZeroMQ documentation is fantastic as well. It inspired and helped shape some of the design choices we made.
The further along we got from design to implementation it became obvious that it would be important to "own" the socket. Generally speaking, this is exactly what ZeroMQ prevents you from doing (and rightly so, it aims to abstract all of that away).
The choice to use Go had an impact here as well. Language features like channels and the breadth of the standard library made it really easy to translate our NSQ design into working code, offsetting the benefit of ZeroMQ's abstractions.
So - this has nothing to do with NSQ - just my $0.02. Maybe zeromq has changed a lot since I looked at it quite a while back. The trouble we constantly ran into was zeromq is really just a fancy socket library - this means that you have to program all the logic yourself if you want certain things to happen if messages cannot be delivered (e.g. log the fact at a minimum), or get queued abnormally long, or get acks from the other side etc.
Which is fine - you have to do all this yourself with plain sockets unless you just need a fire & forget system(albeit with the smarts of retrying and failover and some convenience of pub-sub). However we ran into problems where we could not get the info out of zmq that we wanted, such as the fact a peer had failed, the current rtt, and other things - leaving the gain we'd get from zmq at practically nothing.
We tried to do something along these lines with journly.com. We've since pivoted away and are working on something else, but I agree it's still a problem that needs to be solved.
