4 ms·

But surely this needs to be upgraded to run on a cloud hosted Kubernetes instance? With Karpenter to dynamically scale up an down resources as needed? Supported

But surely this needs to be upgraded to run on a cloud hosted Kubernetes instance? With Karpenter to dynamically scale up an down resources as needed? Supported by a ten people Infosec/SRE team

yard2010 3y ago
Don't forget rewriting the code in Rust because it's faster and type safe! Or nodejs with typescript because it's type safe
- masswerk 3y ago
  Arguably, 8-bit BASIC is type-safe, as well. :-)
  - patates 3y ago
    Totally non-opinionated tried and tested fact that all humanity knows: Anything that doesn't have discriminated unions cannot be used productively.
    - kayodelycaon 3y ago
      Excellent choice of term. I've been a full-stack web developer for over a decade across multiple companies and this is the first time I've seen the phrase "discriminated unions". And the wikipedia article is horrendous. It starts with the following sentence and gets worse from there. > In computer science, a tagged union, also called a variant, variant record, choice type, discriminated union, disjoint union, sum type or coproduct, is a data structure used to hold a value that could take on several different, but fixed, types. It uses lots and lots of words to explain something that's very simple. If you don't already know what it is, you can't figure out which words are important. Then after all of the theory, it dives into a binary tree example which has to be the worst possible way to explain it. If you haven't implemented a binary tree before, you don't know any idea what you're looking at. It didn't help that I implemented a linked list in college. Also, the choice of language ensures you have no idea what the types are. I completely missed the first example was self-referential. It's like parody of a function programmer writing an explanation for anyone who isn't a functional programmer.
      - agentultra 3y ago
        "Simplicity is a great virtue but it requires hard work to achieve it and education to appreciate it." -- Djikstra. I've been programming in some form or another since the late-80s. I've been paid to write code for other people for over twenty years. I haven't gone to university. Maybe it's because I started back in BASIC, assembler, and later C that I know what that term is and have encountered it in various languages and forms several times since? The problem with wikipedia definitions is that they have to be the definition. Some one like me would expect a link to the definition and not a tutorial. They're not written to take into account that you've been a professional programmer and have never been exposed to a computer science curriculum nor are they written for laypersons who don't know anything about programming. It's a similar problem for functional programmers trying to explain functors, monoids, and monads: these are not terribly complicated abstractions but catering your explanation to the various audiences out there is incredibly difficult. The definitions sounds like gibberish... but with effort and education it is possible to understand and appreciate it.
      - TedDoesntTalk 3y ago
        You could edit the wiki page.
    - bentcorner 3y ago
      Care the elaborate? I'm not challenging you I'd just like to learn more. I recently transitioned from writing C++ to Typescript and probably haven't fully grokked the TS way.
      - patates 3y ago
        Oh, I'm so sorry, I was being (or trying to be) sarcastic. However, if you are curious, here is a deep dive: https://basarat.gitbook.io/typescript/type-system/discriminated-unions https://basarat.gitbook.io/typescript/type-system/discrimina... I'm sincerely sorry for confusing you! Discriminated unions are nice but above I was exaggerating excessively to make a point :)
        bentcorner 3y ago
        Hahaha no problem thanks for clarifying :)
  - bitwize 3y ago
    10 DEFINT A-Z
- rewmie 3y ago
  > Don't forget rewriting the code in Rust because it's faster and type safe! I also enjoy piling on Rust fanboys,but those of us who had to go through late night troubleshooting sessions to track issues that were ultimately caused by use-after-free issues do tend to be vulnerable to Rust's memory safety siren's song
- CodeSgt 3y ago
  Typescript is one of the few additional layers of complexity that I truly feel is usually worth it. The exceptions being: a) if you have a complete or near-complete system that functions as intended with no major changes planned for the foreseeable future. And b) the system you’re writing is small, fairly self-contained, and the team isn’t already familiar with Typescript. In any other situation I firmly believe the benefits Typescript brings very quickly outweigh the small amount of added complexity.
masswerk 3y ago
Also, it's really unfair to the ransomeware folks! They need to make a living, too!
throw_5202 3y ago
It's so frustrating to talk to Kubernetes enthusiasts. enthusiast: if you'll migrate service X from a small sets of VMs to K8s cluster (which will take N man-moths because of reasons) it will auto-scale Old grumpy man: but the the load is low and predictable we don't need autoscale and if load will grow we will just create two more VMs enthusiast: auto-scaling will save time in the distant and unlikely future and CTO agrees that K8s is the best way to run software so you have to migrate anyway
- seper8 3y ago
  create two more vms? just give it some more cores/ram/network/disks...
- NikolaNovak 3y ago
  We are running a busy self service ERP for growing 400k employees, on a single database instance for 7 years now. Currently at 256gb ram, 8tb database, 32 P9 cores. I got 99 problems but the single database server ain't one of them!
  - giovannibonetti 3y ago
    Parent was probably talking about the application server, which is the typical example of K8s usage, whereas most databases don't fit well there and are usually separate from the K8s cluster.
    - benglish11 3y ago
      Yeah. They must be. I’ve had several k8s enthusiast dissuade from putting a db in k8s for performance reasons. This may change overtime but I believe there is a performance bottleneck in disk I/o (or at least that’s how it was explained to me)
      - mschuster91 3y ago
        That really depends on your k8s environment. If you're running on bare metal and use host bind mounts for storage, you won't have a problem. But as soon as you introduce shared storage it gets messy...

But surely this needs to be upgraded to run on a cloud hosted Kubernetes instance? With Karpenter to dynamically scale up an down resources as needed? Supported by a ten people Infosec/SRE team

yard2010 3y ago

Don't forget rewriting the code in Rust because it's faster and type safe! Or nodejs with typescript because it's type safe

masswerk 3y ago
Arguably, 8-bit BASIC is type-safe, as well. :-)
- patates 3y ago
  Totally non-opinionated tried and tested fact that all humanity knows: Anything that doesn't have discriminated unions cannot be used productively.
  - kayodelycaon 3y ago
    Excellent choice of term. I've been a full-stack web developer for over a decade across multiple companies and this is the first time I've seen the phrase "discriminated unions". And the wikipedia article is horrendous. It starts with the following sentence and gets worse from there. > In computer science, a tagged union, also called a variant, variant record, choice type, discriminated union, disjoint union, sum type or coproduct, is a data structure used to hold a value that could take on several different, but fixed, types. It uses lots and lots of words to explain something that's very simple. If you don't already know what it is, you can't figure out which words are important. Then after all of the theory, it dives into a binary tree example which has to be the worst possible way to explain it. If you haven't implemented a binary tree before, you don't know any idea what you're looking at. It didn't help that I implemented a linked list in college. Also, the choice of language ensures you have no idea what the types are. I completely missed the first example was self-referential. It's like parody of a function programmer writing an explanation for anyone who isn't a functional programmer.
    - agentultra 3y ago
      "Simplicity is a great virtue but it requires hard work to achieve it and education to appreciate it." -- Djikstra. I've been programming in some form or another since the late-80s. I've been paid to write code for other people for over twenty years. I haven't gone to university. Maybe it's because I started back in BASIC, assembler, and later C that I know what that term is and have encountered it in various languages and forms several times since? The problem with wikipedia definitions is that they have to be the definition. Some one like me would expect a link to the definition and not a tutorial. They're not written to take into account that you've been a professional programmer and have never been exposed to a computer science curriculum nor are they written for laypersons who don't know anything about programming. It's a similar problem for functional programmers trying to explain functors, monoids, and monads: these are not terribly complicated abstractions but catering your explanation to the various audiences out there is incredibly difficult. The definitions sounds like gibberish... but with effort and education it is possible to understand and appreciate it.
    - TedDoesntTalk 3y ago
      You could edit the wiki page.
  - bentcorner 3y ago
    Care the elaborate? I'm not challenging you I'd just like to learn more. I recently transitioned from writing C++ to Typescript and probably haven't fully grokked the TS way.
    - patates 3y ago
      Oh, I'm so sorry, I was being (or trying to be) sarcastic. However, if you are curious, here is a deep dive: https://basarat.gitbook.io/typescript/type-system/discriminated-unions https://basarat.gitbook.io/typescript/type-system/discrimina... I'm sincerely sorry for confusing you! Discriminated unions are nice but above I was exaggerating excessively to make a point :)
      - bentcorner 3y ago
        Hahaha no problem thanks for clarifying :)
- bitwize 3y ago
  10 DEFINT A-Z
rewmie 3y ago
> Don't forget rewriting the code in Rust because it's faster and type safe! I also enjoy piling on Rust fanboys,but those of us who had to go through late night troubleshooting sessions to track issues that were ultimately caused by use-after-free issues do tend to be vulnerable to Rust's memory safety siren's song
CodeSgt 3y ago
Typescript is one of the few additional layers of complexity that I truly feel is usually worth it. The exceptions being: a) if you have a complete or near-complete system that functions as intended with no major changes planned for the foreseeable future. And b) the system you’re writing is small, fairly self-contained, and the team isn’t already familiar with Typescript. In any other situation I firmly believe the benefits Typescript brings very quickly outweigh the small amount of added complexity.

masswerk 3y ago

Also, it's really unfair to the ransomeware folks! They need to make a living, too!

throw_5202 3y ago

It's so frustrating to talk to Kubernetes enthusiasts. enthusiast: if you'll migrate service X from a small sets of VMs to K8s cluster (which will take N man-moths because of reasons) it will auto-scale Old grumpy man: but the the load is low and predictable we don't need autoscale and if load will grow we will just create two more VMs enthusiast: auto-scaling will save time in the distant and unlikely future and CTO agrees that K8s is the best way to run software so you have to migrate anyway

seper8 3y ago
create two more vms? just give it some more cores/ram/network/disks...
NikolaNovak 3y ago
We are running a busy self service ERP for growing 400k employees, on a single database instance for 7 years now. Currently at 256gb ram, 8tb database, 32 P9 cores. I got 99 problems but the single database server ain't one of them!
- giovannibonetti 3y ago
  Parent was probably talking about the application server, which is the typical example of K8s usage, whereas most databases don't fit well there and are usually separate from the K8s cluster.
  - benglish11 3y ago
    Yeah. They must be. I’ve had several k8s enthusiast dissuade from putting a db in k8s for performance reasons. This may change overtime but I believe there is a performance bottleneck in disk I/o (or at least that’s how it was explained to me)
    - mschuster91 3y ago
      That really depends on your k8s environment. If you're running on bare metal and use host bind mounts for storage, you won't have a problem. But as soon as you introduce shared storage it gets messy...