We use Mongo at work and we’ve got some pipelines here and there. Using Monger as the client library

Hi @UE72GJS7J, quite a favour, but would you be up for a chat at some point about them? Doing something similar for our DB Crux and want to get a feel of the pipelines, from someone who has used them.

I’m not an experienced Mongo user (nor much of a fan of it), so I don’t think I can contribute much, sorry. We’re only using it for now because we’re migrating from a legacy Node app, and I haven’t used Mongo outside of this migration. In many places we found pipelines to be very slow, and we’re moving to using Postgres as an additional layer for complex queries. I’ve written a couple of pipelines, and I found that the imperative style of the API is nice and more intuitive than SQL. It’s also easier to compose than SQL, because you’re just dealing with mutable objects, and operations can add or remove keys instead of selecting extra rows. For instance doing a subquery to get the authors of a post, which creates an _author key, and then filtering by _author.email. So I could concat some operations into the pipeline and they don’t need to care about aliases or joins. It was also nice being able to have a query that can then be used to perform a mutation. It reminds me of Datomic’s transaction fns, and Clojure’s transducers. I would love to use a more efficient implementation of Mongo’s pipelines, if only it weren’t Mongo, so I’m excited to see what Crux will do 🙂 Hope that helps some.

it does - thanks 👍

No problem