I had been reading numerous articles comparing MySQL and PostgreSQL and ran across this one. I wish they had mentioned some information about the configuration of the DBMS itself, such as the size of database buffers and query optimization settings.

Also, for their MySQL test procedures, I could not find any information regarding which storage engine they were using. InnoDB is fully ACID-compliant, whereas MyISAM has reduced overhead since it does support transactions and foreign key constraints, for example. I found a good article, http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/ , comparing the two storage engines, and the results were pretty surprising to me.

It ultimately comes down to your individual usage patterns. Using a database abstraction layer will allow you to test your application against different databases so you can see how your application performs first hand.

I've used both and prefer Postgresql. Mysql with MyISAM is "faster" in the same way that bicycling down a hill with no brakes is faster. Mysql 5 with InnoDB is a little bit more serious and is worth considering.

Sounds exactly like what I would expect from a VC and exactly the opposite of what someone like Larry Page would do. I think my energy is better spent fixing valid critiques and requesting a follow-up review once you have.

Better to build something that can stand up to the harshest of reviews than run around spraying perfume on dung.

Anecdotally:

I used to work for "Grand Central Communications". It was really a vision of what not to do with a startup: Enormous development cycle, bleeding money (Hasley Minor, the principle investor and CEO, used to compare it do driving an Audi off the roof of the building every day), way too many people, sales team constantly selling functionality we did not support.

In late 2005 after multiple rounds of layoffs they cut their losses and folded. Existing team members willing to stick around formed Swivel (http://swivel.com) based on what we were working on at the time (which had nothing to do with what Grand Central was doing a year earlier). The name (and I guess trademark) "Grand Central Communications" got inherited by a VOIP company that was also funded by Minor Ventures (http://minorventures.com/) and that's the company O'Reilly is talking about. Good to hear they're turning the name around.

Becoming an SMS spammer is among the 20 smartest startup ideas? That would be pretty sad if it were true.

Our Ruby on Rails app uses PostgreSQL (for now but that will change). We started off with MySQL but after growing quickly, we were forced to look into partitioning of the data. PostgreSQL was made to be easy for advanced stuff like that. We tried to do it with MySQL and failed because we're not MySQL experts and we managed to get it working with Postgres. Postgres has better documentation than MySQL so that might be the factor if you don't have a DBA you can readily ask for help. Here's a write-up by someone who went through similar process:

http://enfranchisedmind.com/blog/archive/2006/11/04/166

Also, if you use Postgres on multi-CPU machines, it's faster than MySQL. But, make sure you read this:

http://www.suite101.com/article.cfm/oracle/115560 (comparison of Oracle/MySQL/PostgreSQL)

One last word of advice if you end up using PostgreSQL, learn and use this:

http://pgreplicator.sourceforge.net/

Finally, we are moving back to MySQL because we found a really fast replacement for the MyISAM storage engine (a lot faster than Postgres) and our part-time DBA knows MySQL and this new storage engine a lot better than Postgres. We are also moving to VPS architecture and Postgres' performance advantage over MySQL on a VPS doesn't really exist.

In the end, go with what your staff/friends know and what your hosting place recommends. If they have an optimized DB stack and provide some kind of a support for it, stick with that DB because you can always go to them for help!

This article is spot-on! As an angel investor, I routinely hear pitches about different mobile apps. My answer is always a big NO and I try everything to persuade small startups that have not spent any money yet on the idea, not to pursue it. If you have an idea for mobile handset market, read about "walled gardens" (google for more links): http://en.wikipedia.org/wiki/Walled_garden_(media)

Unless you have some extremely strong connections (i.e. you have an ex telco exec on the board or as a CEO), stay clear of ALL closed platforms. (Incidentally, and that also includes Windows/MSOffice/Exchange etc).Startups need to be agile and startups have a higher chance of becoming successful if there are less barriers that you need to jump over, not more. This is why Internet is a perfect platform for startups... there are virtually no barriers (unless net-neutrality is defeated)!

What he said really struck home with me, too.

"If you're interested in startups, don't sit around waiting for the perfect opportunity, just go find one that sounds interesting [...] The startup will probably fail, but you will succeed because you have learned a lot more than you otherwise would have."

It's exactly what I've heard so many successful people say.

The startup path is a scary one for me, but spending my life as a "worker bee" is even more scary somehow...

good initiative. well done.