* Posts by liranz

5 publicly visible posts • joined 13 Jul 2011

ScaleBase shatters MySQL for scalability

liranz
Happy

ScaleBase

Thanks. Would love to see you as a customer http://www.theregister.co.uk/Design/graphics/icons/comment/happy_32.png

liranz
Facepalm

Recursive shards

Yes you can... http://www.theregister.co.uk/Design/graphics/icons/comment/facepalm_32.png

liranz

MySQL

Well - MySQL is a very popular database, and there are allot of people with scaling issues around it - so it was a very good fit for us.

liranz

Giant database

I agree - 50GB is not a big database. It depends on the database, machine size and what you do with the database.

However - I disagree that only 1TB databases will enjoy sharding. If you check out our benchmark at http://www.scalebase.com/resources/performance/ you'll see that even a 100GB database got major performance improvements with sharding.

Database high priest mud-wrestles Facebook

liranz

Sharding is not that complex

Stonebraker can say whatever he wants - it doesn't make it the truth. You can read the comments in the original GigaOM post to see what some smart people are saying about his claims (which are off, non technical, and just FUD).

(Disclosure - I work for a newSQL company called ScaleBase). Now if you want to shard you data - there are allot of companies that do that transparently, one of them is ScaleBase. It's possible to shard with relational databases, and it definitely let them scale. Moving to a new database is much crazier than sharding an existing one (unlike what Stonebraker said).