I have been trying to elicit a response from the current maintainers of the
mongodb_ecto packages. I’ve not heard anything yet (if you’re reading, please just let us know what the plan is so we can plan accordingly).
As far as I can tell, those who would wish to use MongoDB + Ecto have:
- In terms of drivers,
mongodb_driver. As has been pointed out, the latter has better support for newer MongoDB features.
- In terms of Ecto, we have
mongodb_ecto which hasn’t received any updates in some time, and the work of Scott and others in the form of a fork.
@scottmessinger’s efforts bring MongoDB + Ecto into a usable state, which is very welcome. I hope Scott you won’t mind me saying though that these are “just the beginning” of a few changes that are needed. There are also features in newer versions of MongoDB that would be nice to support too. In other words, the libraries are in need of TLC, it seems like there are people that are willing to put in the work, but we’re stuck here. My question is for everyone, what should we do to keep things moving forward?
Our current options seem quite undesirable for the community and the current maintainers:
- Another fork
- A separately published and maintained package
- Something else?
I really don’t wish to appear to be being negative or critical of anyone’s efforts here: We have a requirement in our company to use MongoDB in our stack, and it’d be great if we could take advantage of an Ecto + MongoDB integration along the way. That and I believe the community could really use a decent offering in this area. Those are my reasons for continuing to push :).
I should also add that it seems that
mongodb_driver came about in the first place because of a lack of maintenance from the
mongodb driver original from which it draws. I’m all for competition but it’s worth pointing out that the same problem exists there too.