Evernote blog: WhySQL?
blog.evernote.com
Evernote blog: WhySQL?
1–10 of 77 posts
Re: Evernote blog: WhySQL?
#2"But we’re relatively satisfied with sharded MySQL storage for Evernote user account metadata, even though that’s not going to win any style points from the cool kids."
Indeed, hipsters beware!
Re: Evernote blog: WhySQL?
#3Re: Evernote blog: WhySQL?
#4Re: Evernote blog: WhySQL?
#5Does anyone have a link to a decent comparison between MySQL and PostgreSQL? I'm really wondering why so many people use MySQL, even though it supports a lot fewer SQL features than PostgreSQL.
Also, MySQL got commercial entity behind it in its early days which promoted it a lot. In addition, it worked an all platforms, including windows, while Postgres was there just in last couple of years.
Re: Evernote blog: WhySQL?
#6Re: Evernote blog: WhySQL?
#7Storing an entire notebook in a single document would be the most obvious. I use postgres all the time and sql is great, but poo-pooing nosql because it wouldn't work with your relational structure is not the best idea. Also - I have found a hybrid between nosql (mongodb) and sql (postgres) is ideal - who says you need to use a single database?
Re: Evernote blog: WhySQL?
#8Does anyone have a link to a decent comparison between MySQL and PostgreSQL? I'm really wondering why so many people use MySQL, even though it supports a lot fewer SQL features than PostgreSQL.
MySQL is good enough so there is no need to migrate applications for a few additional features.
Re: Evernote blog: WhySQL?
#9Also, the example itself is very weak as bitdiffusion below pointed out.