Kinda begging the question aren't we? I turn to nosql for things that aren't key-value, generally.
What do you mean? Isn't NoSQL inherently key-value?
Scaling to 100M: MySQL Is a Better NoSQL
11–20 of 183 posts
Re: Scaling to 100M: MySQL Is a Better NoSQL
#12And PostgreSQL is a better MySQL so... all is settled?
Is it? MySQL improved a lot since 5.1 days, you know.
That's true, and I don't doubt that many developers' opinion of MySQL is tainted by some of the issues in earlier versions. It's still difficult to see what newer versions offer over Postgres though - and Postgres has a lot of bonus features too (like the JSON storage types, which are sublime)
Re: Scaling to 100M: MySQL Is a Better NoSQL
#13This is basically "We made it work, easy, all the rest are wrong".
Wix is 10 years old, they probably started with MySql and stuck with it, is it wrong? Maybe, maybe not.
If they were to start today would they have used Mysql aswell or gone with another solution?
Did they spend the last 10 years building tools to help them scale MySql (at which point it's easy for them to operate) rather than use a tool that had multi server or multi DC in-mind.
Oh and citing statistics without details is plain lying, how many server, how much RAM, SSD based or HDD....
Re: Scaling to 100M: MySQL Is a Better NoSQL
#14Since Wix is using MySQL as a key-store ... I wonder why they didn't look at using Postgres HStore [1]. HStore is a key value store built directly in the RDBMS of Postgres. [1] http://www.postgresql.org/docs/9.6/static/hstore.html
Hstore has a lot of issues in my experience. Very hard to query through most ORMs, expensive indexes, strings only, not nested data, lots of unoptimized parsers out there relative to json. Use jsonb if you want postgres KV storage.
Hstore is more k->k->v, which is the same but different, and also leads inexperienced developers to model entire relationships in a single column
Re: Scaling to 100M: MySQL Is a Better NoSQL
#15This may be an unpopular perspective, but here goes. For many years I ran a business doing web development. I had many clients approach me who were using Wix, and who I could not help, because Wix had effectively taken hostage their images. Because of those years of bad experiences (telling clients that they are screwed unless they keep paying Wix), I do not trust Wix, and so I do not trust this post. Should those clients have trusted that Wix would make their data available in the future? No, totally not. But that is the cost of doing shady things. Everything with your name on it now gets taken with a grain of salt.
Re: Scaling to 100M: MySQL Is a Better NoSQL
#16>An active-active-active setup across three data centers. Any info how "active-active-active" (I assume 3 aws regions) is accomplished?
Some kind of master-master replication, probably: https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-replic...
Re: Scaling to 100M: MySQL Is a Better NoSQL
#17Kinda begging the question aren't we? I turn to nosql for things that aren't key-value, generally.
What do you mean? Isn't NoSQL inherently key-value?
Are graph databases key/value? Are document databases key/value?
Try this:
https://en.wikipedia.org/wiki/NoSQL#Types_and_examples_of_No...
Re: Scaling to 100M: MySQL Is a Better NoSQL
#18This is basically "We made it work, easy, all the rest are wrong". Wix is 10 years old, they probably started with MySql and stuck with it, is it wrong? Maybe, maybe not. If they were to start today would they have used Mysql aswell or gone with another solution? Did they spend the last 10 years building tools to help them scale MySql (at which point it's easy for them to operate) rather than use a tool that had mult…
Reddit does something very similar. https://kev.inburke.com/kevin/reddits-database-has-two-table...
I think the important thing to note here is that there are lots of different ways to use any given tool that can fit your use case without being an atrocity.
Re: Scaling to 100M: MySQL Is a Better NoSQL
#19Kinda begging the question aren't we? I turn to nosql for things that aren't key-value, generally.
What do you mean? Isn't NoSQL inherently key-value?
No. Triplestores and Graph databases aren't key-value stores. There's more to NOSQL than key value stores although most examples seem to be.
Re: Scaling to 100M: MySQL Is a Better NoSQL
#20Earlier quoted context omitted.
Is it? MySQL improved a lot since 5.1 days, you know.
That's true, and I don't doubt that many developers' opinion of MySQL is tainted by some of the issues in earlier versions. It's still difficult to see what newer versions offer over Postgres though - and Postgres has a lot of bonus features too (like the JSON storage types, which are sublime)
I'm a big believer in PostgreSQL but it does have one large and glaringly bad area which needs addressing: distribution. MySQL does Master-Master well. PostgreSQL has been a "chose your own adventure" for a long, long time. With the changes they're planning to make to allow better replication, that will change. Right now, MySQL has that aspect beat.