3 ms·

Why so hostile? Personally, I assume this is just an instance of them not being PostgeSQL experts. So, before jumping to conclusions (namely that they deliberat

Why so hostile? Personally, I assume this is just an instance of them not being PostgeSQL experts. So, before jumping to conclusions (namely that they deliberatly skewed their test, despite being very open in the way they described the setup), I'll instead wait and see -- perhaps they'll explain why they used json instead of jsonb, or perhaps (better!) they can updat the test to also include jsonb.

swasheck 11y ago
> I assume this is just an instance of them not being PostgeSQL experts. this illuminates the need for "experts" in the different components in the stack. it's intellectually dishonest to claim that a technology is not up to the task when it's not been properly treated in the first place.
SuperKlaus 11y ago
If they're not Postgres experts then they shouldn't be including Postgres in the line-up. Or ask someone that ask someone that knows better.
- X4lldux 11y ago
  That's why they welcome pull-requests.
k__ 11y ago
They wanted to play with the other kids, but no one invited them, so they threw their own party despite not knowing how to throw one. Biggest problem of (small) German tech companies IMO. I worked for one myself and they had really good core technology, but that was it. The angelo-saxon companies always outplayed them, because they're just so much better at PR. Even their developers are better at this than most marketeers that burn money on a daily basis in Germany...
chucky_z 11y ago
I think his hostility comes from the fact that if you google just "postgresql json" the second hit is the official documentation that goes over jsonb right in the second paragraph. http://www.postgresql.org/docs/9.4/static/datatype-json.html http://www.postgresql.org/docs/9.4/static/datatype-json.html You can also see that the very first link outside of the official documentation: https://www.compose.io/articles/is-postgresql-your-next-json-database/ https://www.compose.io/articles/is-postgresql-your-next-json... Explains the benefits of jsonb and how to use indexes. If you're going to include a database, at the very least do 20 minutes of research on it. If that can't be given, then just don't include something. That's like saying "I've just installed MongoDB and read the intro documentation page, I'm now going to benchmark it against a MySQL cluster, which I have years of experience with, and that I helped develop." (E.g.: they developed ArangoDB, so they should be experts in at least that, right?)
creshal 11y ago
> Why so hostile? Personally, I assume this is just an instance of them not being PostgeSQL experts. Postgres' official documentation on json and jsonb is rather concise: http://www.postgresql.org/docs/9.4/static/datatype-json.html http://www.postgresql.org/docs/9.4/static/datatype-json.html The difference between the types is described in paragraph two. So, they either benchmarked Postgres while having no idea whatsoever what they were doing, or they were deliberately crippling the competition. Neither option is confidence inspiring. (And the first option seems sketchy, seeing how they then went and re-created the whole benchmark as classical RDBMS setup for the second postgres test.)

swasheck 11y ago

> I assume this is just an instance of them not being PostgeSQL experts. this illuminates the need for "experts" in the different components in the stack. it's intellectually dishonest to claim that a technology is not up to the task when it's not been properly treated in the first place.

SuperKlaus 11y ago

If they're not Postgres experts then they shouldn't be including Postgres in the line-up. Or ask someone that ask someone that knows better.

X4lldux 11y ago
That's why they welcome pull-requests.

k__ 11y ago

They wanted to play with the other kids, but no one invited them, so they threw their own party despite not knowing how to throw one. Biggest problem of (small) German tech companies IMO. I worked for one myself and they had really good core technology, but that was it. The angelo-saxon companies always outplayed them, because they're just so much better at PR. Even their developers are better at this than most marketeers that burn money on a daily basis in Germany...

chucky_z 11y ago

I think his hostility comes from the fact that if you google just "postgresql json" the second hit is the official documentation that goes over jsonb right in the second paragraph. http://www.postgresql.org/docs/9.4/static/datatype-json.html http://www.postgresql.org/docs/9.4/static/datatype-json.html You can also see that the very first link outside of the official documentation: https://www.compose.io/articles/is-postgresql-your-next-json-database/ https://www.compose.io/articles/is-postgresql-your-next-json... Explains the benefits of jsonb and how to use indexes. If you're going to include a database, at the very least do 20 minutes of research on it. If that can't be given, then just don't include something. That's like saying "I've just installed MongoDB and read the intro documentation page, I'm now going to benchmark it against a MySQL cluster, which I have years of experience with, and that I helped develop." (E.g.: they developed ArangoDB, so they should be experts in at least that, right?)

creshal 11y ago

> Why so hostile? Personally, I assume this is just an instance of them not being PostgeSQL experts. Postgres' official documentation on json and jsonb is rather concise: http://www.postgresql.org/docs/9.4/static/datatype-json.html http://www.postgresql.org/docs/9.4/static/datatype-json.html The difference between the types is described in paragraph two. So, they either benchmarked Postgres while having no idea whatsoever what they were doing, or they were deliberately crippling the competition. Neither option is confidence inspiring. (And the first option seems sketchy, seeing how they then went and re-created the whole benchmark as classical RDBMS setup for the second postgres test.)