Comments on: Choosing a Database http://blog.vikido.com/choosing-a-database?utm_source=rss&utm_medium=rss&utm_campaign=choosing-a-database Vikido - Safe Social Network for Families Mon, 03 Oct 2011 15:14:48 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Yair http://blog.vikido.com/choosing-a-database/comment-page-1#comment-15 Yair Fri, 12 Jun 2009 12:17:36 +0000 http://www.vikido.com/Blog/?p=12#comment-15 If you need a full scale relational DB, I'd go with MySQL. If all you actually need is a large and efficient hash table, I would check out some other alternatives. In <a href="http://yairwein.blogspot.com/2009/04/he-who-could-not-be-named.html" rel="nofollow">this</a> post I describe the alternative that I've been using, and there is a link inside the post to a detailed survey of other alternatives. Good luck! If you need a full scale relational DB, I’d go with MySQL. If all you actually need is a large and efficient hash table, I would check out some other alternatives. In this post I describe the alternative that I’ve been using, and there is a link inside the post to a detailed survey of other alternatives. Good luck!

]]> By: Ehud Rosenberg http://blog.vikido.com/choosing-a-database/comment-page-1#comment-6 Ehud Rosenberg Wed, 20 May 2009 10:26:42 +0000 http://www.vikido.com/Blog/?p=12#comment-6 Unless you're building a super real time web application - there is no real question IMO. If you're using PHP go with mysql (or postgresql if you're more adventures). BTW - I know it may sound fanboy-ish, but have you considered RoR instead of whatever PHP framework you're using? Unless you’re building a super real time web application – there is no real question IMO. If you’re using PHP go with mysql (or postgresql if you’re more adventures).

BTW – I know it may sound fanboy-ish, but have you considered RoR instead of whatever PHP framework you’re using?

]]> By: Tzury Bar Yochay http://blog.vikido.com/choosing-a-database/comment-page-1#comment-4 Tzury Bar Yochay Mon, 18 May 2009 18:32:05 +0000 http://www.vikido.com/Blog/?p=12#comment-4 have a look here (http://www.mail-archive.com/couchdb-user@incubator.apache.org/msg01506.html) about the first question you should ask, table based vs. schema-free document-oriented database. Have you considered aws? (you probably did) Anyway, to get hte best answeres for this kind of question you should post this question at http://news.ycombinator.com/ (and some others that will come by as you progress wit hthe startup) have a look here (http://www.mail-archive.com/couchdb-user@incubator.apache.org/msg01506.html) about the first question you should ask, table based vs. schema-free document-oriented database.

Have you considered aws?
(you probably did)

Anyway, to get hte best answeres for this kind of question you should post this question at http://news.ycombinator.com/ (and some others that will come by as you progress wit hthe startup)

]]> By: טל http://blog.vikido.com/choosing-a-database/comment-page-1#comment-3 טל Mon, 18 May 2009 13:25:09 +0000 http://www.vikido.com/Blog/?p=12#comment-3 There are so many things to take into consideration before choosing a db that it will require much more information in order to provide an educated suggestion. Every database has its own strengths and weaknesses. For example, an oracle db will be the best for scalability and performance (for big databases). On the other hand, price and ease-of-use are not among its strengths. Of course, no one can beat MySql's Price. My advice would be to use database that your database professional is most comfortable with. if you don't have a database guy, get one because it looks like your application will require a lot of database heavy lifting. It is important to take into consideration the cost of the human factor (training and salaries) because it varies between db’s. For bootstrapping, I would start with MySql and try to write database agnostic code. This will help if you will need to switch the db later. Just my $0.02. ( am I really the first commenter on this blog?) There are so many things to take into consideration before choosing a db that it will require much more information in order to provide an educated suggestion.
Every database has its own strengths and weaknesses. For example, an oracle db will be the best for scalability and performance (for big databases). On the other hand, price and ease-of-use are not among its strengths. Of course, no one can beat MySql’s Price.
My advice would be to use database that your database professional is most comfortable with. if you don’t have a database guy, get one because it looks like your application will require a lot of database heavy lifting. It is important to take into consideration the cost of the human factor (training and salaries) because it varies between db’s.
For bootstrapping, I would start with MySql and try to write database agnostic code. This will help if you will need to switch the db later.
Just my $0.02. ( am I really the first commenter on this blog?)

]]>