admataz
commented
6 years ago great topic - and highly relevant to a lot us.
While we're on the subject: Apart from developer experience and maintainability of schema you mention - Mongoose has come under a lot of criticism for performance (I'm thinking specifically of populate and doing expensive stuff application side that would be handled better by a relational database) - I'd be interested to hear what you think about this aspect too (or if that's a subject for another talk?!)
xscheiner
Mongoose has helped us greatly to maintain the integrity of our data against a mongodb database. However, we are not able to share the models we use on our apis anywhere outside those apis. And Mongoose schemas are not shareable, which means we cannot consume them on any other level of our applications. This means either using conversion plugins, or else writing and maintaining some other solution. In addition, the mongoose models themselves are not shareable, which means even if we solve the schema issue, we still have at least two sets of models to maintain.
Finally, we use Typescript, which means ideally we can share schema definitions with that which would allow us to define our entities once and have those definitions propagate to all levels of our applications.
The final part of this presentation will focus on the solution we now intend to adopt as we begin to overhaul our entire architecture in the coming months.