mongodb - Rearchitecture ASP.NET app by replacing SQL Server with NoSQL -


There is an ASP.NET app with our SSP server; This is a photo & amp; Video sharing site photo and video details are stored in tables & amp; Files are in the file system.

The database has 75 tables and 225 stored processes, the app will be ready for production deployment within next 6 months.

Due to the concern of the long-term increase, we decided to switch to the NoCQL ( MongoDB ) database.

  • Is it better to deploy the app with SQL Server backend and then migrate to the NoCQB?

  • Or re-write / re-architecture and database, tables, procedures and data layer

  • This How difficult would it be to become architectural / recursive MongoDB? Any device or BKM?

    Edit: Our app is Youtube + Flickr type site where users will share photos and videos with many comments, tags and ratings (photos \ Videos and comments).

    Is NOSQL to Move Better Database? The reason for moving forward: Cost + read speed of the query

    Please give me valuable advice with you.

    Thank you very much.

    The change is always more expensive, later it is offered for a project. This is the main principle of software engineering, you should do it now

    He said, I ask questions with your long term vision. Relational databases are used properly, they have a lot of performance.

Comments