6 ms·

Some of these issues were solved by Spark. Do agree with the overall point, people shouldn’t be reaching for Hadoop when Postgres would suffice. Indexes are fas

Some of these issues were solved by Spark. Do agree with the overall point, people shouldn’t be reaching for Hadoop when Postgres would suffice. Indexes are fast. Use them.

ysofunny 3y ago
> people shouldn’t be reaching for Hadoop when Postgres would suffice. Indexes are fast. Use them. let me try a riskier one: "people should not be reaching for kubernetes when a system administrator would suffice. sysadmins are cheap(er?) than clouds, use them" it did not come out very well.... I got stuck trying to find what to contrast kube with; all I got in them minutes alloted to comment posting was 'system administrator'. meh.
- rijx 3y ago
  Nowadays K3s is worth the small learning curve with a big payoff as you get a lot of automation included / by installing an operator :-)
  - jt2190 3y ago
    > … K3s… I’m assuming this isn’t a typo and you mean Kubes? https://kubes.guru/getting-started/ https://kubes.guru/getting-started/
    - maxcoder4 3y ago
      I don't know what OP meant, but https://k3s.io/ https://k3s.io/ also fits the context.
      - Areading314 3y ago
        K8s is an abbreviation of kubernetes K3s is an abbreviation of k8s
        eichin 3y ago
        ... wouldn't that be k1s?
      - rijx 3y ago
        Yes, I meant this K3s as it's trivial to deploy and quite mature by now.
        jt2190 3y ago
        Thanks for confirming.
- dunk010 3y ago
  Everyone wants to use k8s and like 1% need it in any shape or form. It basically acts as a conspiracy between otherwise-redundant ops level people and those running Kubernettes against the companies who have to pay for all this. Just use Fargate, and be done.
- nurettin 3y ago
  I thought you still need a sysadmin or whoever is needed to set up and maintain kubernetes.
- threeseed 3y ago
  > sysadmins are cheap(er?) than clouds, use them This is just another lazy take. There are many reasons why companies move to the cloud. Cost is not the only consideration.
kevindamm 3y ago
Indexes are fast when they're built well and used often. Indexes are expensive (and paid for in triplicate via backup costs) when they are seldom or never used. Sometimes you just need to materialize a table temporarily, which of course you can do in the RDBMS as well, but sometimes the data sources are so scattered (or also ephemeral) that keeping all processing inside the DB system is a stretch. But perhaps the most compelling justification is based on the DB systems familiarity on the team. Not everyone has the same level of SQL expertise and some of the visualization tools added to MapReduce systems and the source language itself are more familiar to them than the output of an EXPLAIN statement. Especially if the same pipeline is effectively hundreds of lines in SQL.
woooooo 3y ago
If you're doing analytics that require full table scans, indices are pure overhead. No database will beat just piping all the records through some process for full scans.

Some of these issues were solved by Spark. Do agree with the overall point, people shouldn’t be reaching for Hadoop when Postgres would suffice. Indexes are fast. Use them.

ysofunny 3y ago

> people shouldn’t be reaching for Hadoop when Postgres would suffice. Indexes are fast. Use them. let me try a riskier one: "people should not be reaching for kubernetes when a system administrator would suffice. sysadmins are cheap(er?) than clouds, use them" it did not come out very well.... I got stuck trying to find what to contrast kube with; all I got in them minutes alloted to comment posting was 'system administrator'. meh.

rijx 3y ago
Nowadays K3s is worth the small learning curve with a big payoff as you get a lot of automation included / by installing an operator :-)
- jt2190 3y ago
  > … K3s… I’m assuming this isn’t a typo and you mean Kubes? https://kubes.guru/getting-started/ https://kubes.guru/getting-started/
  - maxcoder4 3y ago
    I don't know what OP meant, but https://k3s.io/ https://k3s.io/ also fits the context.
    - Areading314 3y ago
      K8s is an abbreviation of kubernetes K3s is an abbreviation of k8s
      - eichin 3y ago
        ... wouldn't that be k1s?
    - rijx 3y ago
      Yes, I meant this K3s as it's trivial to deploy and quite mature by now.
      - jt2190 3y ago
        Thanks for confirming.
dunk010 3y ago
Everyone wants to use k8s and like 1% need it in any shape or form. It basically acts as a conspiracy between otherwise-redundant ops level people and those running Kubernettes against the companies who have to pay for all this. Just use Fargate, and be done.
nurettin 3y ago
I thought you still need a sysadmin or whoever is needed to set up and maintain kubernetes.
threeseed 3y ago
> sysadmins are cheap(er?) than clouds, use them This is just another lazy take. There are many reasons why companies move to the cloud. Cost is not the only consideration.

kevindamm 3y ago

Indexes are fast when they're built well and used often. Indexes are expensive (and paid for in triplicate via backup costs) when they are seldom or never used. Sometimes you just need to materialize a table temporarily, which of course you can do in the RDBMS as well, but sometimes the data sources are so scattered (or also ephemeral) that keeping all processing inside the DB system is a stretch. But perhaps the most compelling justification is based on the DB systems familiarity on the team. Not everyone has the same level of SQL expertise and some of the visualization tools added to MapReduce systems and the source language itself are more familiar to them than the output of an EXPLAIN statement. Especially if the same pipeline is effectively hundreds of lines in SQL.

woooooo 3y ago

If you're doing analytics that require full table scans, indices are pure overhead. No database will beat just piping all the records through some process for full scans.