[timewarrior]

I am not sure what is the exact use case. They could be using it for a non-critical data warehouse which could easily be recreated.

If you can deterministically determine your use case and are confident that mongo will fit it - it might be a good idea.

My concern which mongo is that is if you push the feature set, it will start falling apart at the seams.

Even though Postgres/MySql have some issues which can reduce the velocity of your team, if you absolutely want to be sure about data integrity and want full flexibility of evolving use case, they might serve better than mongo.

[girishso]

> I am not sure what is the exact use case. They could be using it for a non-critical data warehouse which could easily be recreated.

They decided to port the existing project to .NET and used MongoDB (just because the .NET team thought it's cool) to store _all the data_, I'm pretty sure of it. My friend was not part of the .NET team.