I am currently developing prototypes of a web application that collects large number of text entries from a large number of users Does. This data should often be displayed back and updated frequently. At the moment I store the contents within a MySQL database and use the NHibernate ORM layer to interact with DB. I have found a table defined for users, roles, presentations, tags, notifications, etc. I like this solution because it works well and my code looks good and sensible, but I'm also worried about how once the size of MySQL will be displayed, it reaches a significant number of our databases. That it can struggle to accelerate the expedition to accelerate the campaign.
It has given me a non-relational database system like, or, unfortunately, I have no experience. I have read some good reviews on MongoDB and it seems interesting I am happy to spend time learning Is there a way to go out? Do I appreciate any point or point of view to go with any relational DBM?
Other answers here are mainly centered on technical aspects, but I think the important points are Focusing on the startup company aspect of those things:
- Taking advantage of talent MySQL is very common and you will probably be able to find (more importantly, cheapest) to find developers than it would be for a more discounted database system. This big developer base also means more tutorials, a more active support community etc.
- The ease of development Again, because MySQL is so common, you will know that DB of choice for great systems / services, this common ground can make any external integration a bit easier.
- You are preparing for a situation that can never exist, and if it does, then it is manageable. Very few businesses (never started) come close to MySQL borders, and with all respect (and I'm guessing here); It's likely that your startup will fail to shut down properly structured, well-resourceed MySQL dbs, like data throughput.
Actually, do not spend your time (== money) which are concerned about using DB, as well as lots of MySQL data Can handle, well-proven and well-supported.
Returning to the technical side of things ... something that has more impact on the speed of your app compared to DB's choice, how efficiently the data Cached may have a dramatic effect on reducing an effective cache DB load and accelerating the normal responsiveness of an app. I look into cached solutions and you are developing your app so that it can make the best use of those solutions. I will spend time checking my choice for caching solution.
FYI, My Caching solution of choice
Comments
Post a Comment