Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The other answers here have focused mainly on the technical aspects, but I think there are important points to be made that focus on the <em>startup company</em> aspect of things:</p> <ul> <li><em>Availabililty of talent.</em> MySQL is very common and you will probably find it easier (and more importantly, cheaper) to find developers for it, compared to the more rarified database systems. This larger developer base will also mean more tutorials, a more active support community, etc.</li> <li><em>Ease of development.</em> Again, because MySQL is so common, you will find it is the db of choice for a great many systems / services. This common ground may make any external integration a little easier.</li> <li><em>You are preparing for a situation that may never exist, and is manageable if it does.</em> Very few businesses (nevermind startups) come close to MySQL's limits, and with all due respect (and I am just guessing here); the likelihood that your startup will ever hit the sort of data throughput to cripple a properly structured, well resourced MySQL db is almost zero.</li> </ul> <p>Basically, don't spend your time ( == money) worrying about which db to use, as MySQL can handle <em>a lot</em> of data, is well proven and well supported.</p> <p>Going back to the technical side of things... Something that will have a <em>far</em> greater impact on the speed of your app than choice of db, is how efficiently data can be <strong>cached</strong>. An effective cache can have dramatic effects on reducing db load and speeding up the general responsivness of an app. I would spend your time investigating caching solutions and making sure you are developing your app in such a way that it can make the best use of those solutions.</p> <p>FYI, my caching solution of choice is <a href="http://memcached.org/" rel="noreferrer">memcached</a>. </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload