5 ms·

It's not worth pointing out the technical flaws in the post[1]. It is obvious the author does not have a strong grasp of the tools he is criticising. A better e

It's not worth pointing out the technical flaws in the post[1]. It is obvious the author does not have a strong grasp of the tools he is criticising. A better example of this style of post is Oxide's evaluation[2] for control plane storage that actually goes over their specific needs and context. [1] Ok, just one, Rick Houlihan is currently at MongoDB. [2] https://rfd.shared.oxide.computer/rfd/53 https://rfd.shared.oxide.computer/rfd/53

wordofx 2y ago
Na. The post is good.
worik 2y ago
> Rick Houlihan is currently at MongoDB. Not according to the YT video. AWS in 2018 I did not detect technical flaws in the article. I thought it was very good
- arpinum 2y ago
  [flagged]
  - jb1991 2y ago
    > The author asked where Rick is today and got his name wrong. That is not what is called a “technical flaw“.
  - emccue 2y ago
    Yeah, shit. Fixed that one. Would you believe I don't have an editor?
marcus0x62 2y ago
> It's not worth pointing out the technical flaws in the post[1]. It might help your argument if you pointed out a real technical flaw in the content of the post, and not an example of the author being mistaken about a stranger's first name.
- arpinum 2y ago
  sure. 1. sqlite can have more than 1 file when using wal mode. 2. You don't need to know your exact dyanmodb access patterns upfront, you can evolve the schema. again, not worth effort to point out more.
  - mbb70 2y ago
    Denormalizing data always locks you into certain access patterns, regardless of your ability to evolve schema.
    - endisneigh 2y ago
      You do not have to denormalize data to use dynamodb, just like how data doesn’t have to be normalized to use a relational DB. Man people have no clue what they’re talking about lol
    - kikimora 2y ago
      DynamoDb is not a distributed hash map, it is a distributed forest of B-Trees. And B-Trees are what PG uses for indices and MySQL for both tables and indices. You don’t demoralize with it, but rather you build and maintain table and index like structures, they would contain submitted of ids or other data fields but it is the same with normal DB indexes. The difference if you have to maintain them manually. The upside is scale, serverlessnes and maybe less latency.
  - laurent_du 2y ago
    I believe what the author has in mind is the fact that you need to create your LSI at the same time as you create the table, you cannot add them later (until GSI). So there's some truth to what they are saying regarding access patterns.

wordofx 2y ago

Na. The post is good.

worik 2y ago

> Rick Houlihan is currently at MongoDB. Not according to the YT video. AWS in 2018 I did not detect technical flaws in the article. I thought it was very good

arpinum 2y ago
[flagged]
- jb1991 2y ago
  > The author asked where Rick is today and got his name wrong. That is not what is called a “technical flaw“.
- emccue 2y ago
  Yeah, shit. Fixed that one. Would you believe I don't have an editor?

marcus0x62 2y ago

> It's not worth pointing out the technical flaws in the post[1]. It might help your argument if you pointed out a real technical flaw in the content of the post, and not an example of the author being mistaken about a stranger's first name.

arpinum 2y ago
sure. 1. sqlite can have more than 1 file when using wal mode. 2. You don't need to know your exact dyanmodb access patterns upfront, you can evolve the schema. again, not worth effort to point out more.
- mbb70 2y ago
  Denormalizing data always locks you into certain access patterns, regardless of your ability to evolve schema.
  - endisneigh 2y ago
    You do not have to denormalize data to use dynamodb, just like how data doesn’t have to be normalized to use a relational DB. Man people have no clue what they’re talking about lol
  - kikimora 2y ago
    DynamoDb is not a distributed hash map, it is a distributed forest of B-Trees. And B-Trees are what PG uses for indices and MySQL for both tables and indices. You don’t demoralize with it, but rather you build and maintain table and index like structures, they would contain submitted of ids or other data fields but it is the same with normal DB indexes. The difference if you have to maintain them manually. The upside is scale, serverlessnes and maybe less latency.
- laurent_du 2y ago
  I believe what the author has in mind is the fact that you need to create your LSI at the same time as you create the table, you cannot add them later (until GSI). So there's some truth to what they are saying regarding access patterns.