4 ms·
I have been developing with MongoDB for about the past year. (Briefly, I have developed, and continue to support, an ASP.NET MVC C# Web Application that's used
by 127001brewer 12y ago
I have been developing with MongoDB for about the past year. (Briefly, I have developed, and continue to support, an ASP.NET MVC C# Web Application that's used by a few thousand people daily. For my personal projects that use MongoDB, I develop with PHP and Python.)
Overall, I enjoy working with MongoDB, because it (generally) maps directly to your object - there is no need for an additional layer (such as an Object Relational Mapper (ORM)).
However, you have to be more careful with your data structure. For example, having sub-arrays in sub-arrays is probably not a good idea.
I will be happy to share more, so feel free to look up my profile.
- msandford 12y agoI ran a website and operations for a company that did over 1mm a year in revenue. Everything was done off of a single machine that was the webserver, database server and media server. Had 10k customers all of whom were active daily. Postgres and Python/Django and I never saw load averages much over 10%. Unless you have a substantial fraction of a million daily users you probably don't need mongo.
- 127001brewer 12y agoI agree with that MongoDB may have been overkill, but my web application's architecture was chosen before I joined the team.