This is fine and well if you're using your team's language tooling to enforce these things. But the moment you're outside those boundaries all bets are off.
Re:Was MongoDB Ever the Right Choice?
by scarface74 on Wednesday March 27, 2019 @08:15AM
(#19500082)
Even if I’m using an RDMS, as a tech lead, I still enforce only one “service” writes to a particular set of domain related tables. I don’t mean an http microservice necessarily. It could very well be a separate project/module in a monolith or even a package/module shared via an internal package manager.
But I would never use a weakly typed language and a weakly typed data store. That’s a mess waiting to happen.
Custom query language - I bet he also hates ElasticSearch. But again, using C# and the first party Mongo LINQ library, you are working with LINQ - the same built in C# query language that every C# developer should be familiar with. One of the requirements I wrote when I was hiring contractors for a Mongo based project was familiarity with Entity Framework. Even though we wouldn’t be using EF, if they knew it, it would be seamless to transition over to Mongo/LINQ.
Edit:
And as a side note, creating your “application defined schema” from a pre-existing JSON document, is a simple matter of copying the JSON to:
http://json2csharp.com/