Chartio develops non-blocking MySQL queries using Tornado

Re:Chartio develops non-blocking MySQL queries using Tornado by IgorPartola on Friday June 10, 2011 @03:39PM (#2642133)

Some reasons:

* It's already in place

* Everyone on your team only knows MySQL

* That's what you know and you are under a deadline

* It's the right tool for the job (as opposed to something very different, from the NoSQL world)

* You are using MySQL Cluster instead of MySQL, but don't have the cash to upgrade to Oracle

[ Parent | on HN ]

Re:Chartio develops non-blocking MySQL queries using Tornado by Luyt on Friday June 10, 2011 @09:57PM (#2642991)

"It's the right tool for the job (as opposed to something very different, from the NoSQL world)"

If I may toot my own horn, I just upgraded the layout of http://mongodb-is-web-scale.com/ so that you can scroll while the video stays visible.

[ Parent | on HN ]

Re:Chartio develops non-blocking MySQL queries using Tornado by invisible on Saturday June 11, 2011 @12:44AM (#2643229)

Believe it or not, sometimes mongodb is the perfect tool for the job. It actually does support safe wrriting features, so some of the hype in that video is false. MySQL is always a great piece of the stack but it's not always good.

[ Parent | on HN ]

Re:Chartio develops non-blocking MySQL queries using Tornado by Luyt on Saturday June 11, 2011 @07:18AM (#2643647)

The video also shows its age, MongoDB hasn't stood still in the meantime. I put up a transcript of this movie because I found the mingling of the technical discussion with contemplating working on a horrible farm an interesting concept.

[ Parent | on HN ]

Re:Chartio develops non-blocking MySQL queries using Tornado by thingsilearned on Friday June 10, 2011 @03:50PM (#2642171)

In all of our surveys (of web companies) the majority of people use MySQL. That certainly doesn't mean that its the best choice but using the most common software does come with a lot of obvious benefits.

http://news.ycombinator.com/item?id=1411937

[ Parent | on HN ]

Re:Chartio develops non-blocking MySQL queries using Tornado by fauigerzigerk on Saturday June 11, 2011 @05:30AM (#2643537)

It has a lot of weaknesses compared to postgres but it also has some definite advantages:

Clustered and covering indexes. If the data needed by a query is in an index there is no need to retrieve it from the table itself. This leads to better memory usage and cache locality.

MySQL has non transactional tables which use a lot less memory. If you store a large number of small records (say three ints or something) that table will use about a third of the memory a similar postgres (or Oracle) table would.

[ Parent | on HN ]

Re:Chartio develops non-blocking MySQL queries using Tornado by jbooth on Friday June 10, 2011 @05:30PM (#2642495)

Why would you use anything else?

Mysql:

- Never crashes

- Has more tested/reliable replication than anything else, possibly including Oracle (haven't tried the wacky 3rd party replication things like Goldengate or whatever, and don't believe in spending 6 figures on software licenses in general).

- Supports SELECT, INSERT and UPDATE

Why would I get anything else for a database? For more complicated stuff I have another approach that I employ called "programming".

[ Parent | on HN ]

Re:Chartio develops non-blocking MySQL queries using Tornado by CoffeeDregs on Friday June 10, 2011 @09:39PM (#2642967)

We're a bit off-topic, but... Transactions on DDL, a lack of tons of gotchas, good replication, partial indexes, document orientation and querying, a pretty query language, ripping speed, horizontal scalability, a history of good architecture, consistent hashing, etc are reasons to select something other than MySQL.

[ Parent | on HN ]

Re:Chartio develops non-blocking MySQL queries using Tornado by revorad on Friday June 10, 2011 @06:00PM (#2642579)

chart.io connects to their customers' databases, which include MySQL among others.

[ Parent | on HN ]