7 ms·

Nice one :-) “… => Thus, we build a monolith service for each app, which is easy to deploy and maintain. No Docker, no Kubernetes, no dependencies, no runtime

Nice one :-) “… => Thus, we build a monolith service for each app, which is easy to deploy and maintain. No Docker, no Kubernetes, no dependencies, no runtime environment - just a binary file that can be deployed on any newly created VPS. …”

tuwtuwtuwtuw 3y ago
I don't use TablePlus myself. Are they talking about their marketing website? If so, then obviously thet wouldn't need to use Kubernetes. Are they talking about their application then I wonder how there can be no dependencies - don't it store data, log things, etc?
- tux3 3y ago
  You can store data by connecting to a database, and you can store logs by either sending them to the system journal and having a daemon collect them, or sending them to whatever cloud you like using a logging library. It's fine, really. Those database and logging services you can put in a docker if you like, but if you put them anywhere else it works just the same. A Postgres in k8s or a Postgres on a dedicated server is the same as far as the client is concerned.
  - tuwtuwtuwtuw 3y ago
    But isn't that software you download and run in your own environment? I'm mostly not following what is under a DDoS attack. Is it their web page mostly consisting of marketing material with static pages?
    - gnuvince 3y ago
      > I'm mostly not following what is under a DDoS attack. Is it their web page mostly consisting of marketing material with static pages? Yes.
      - tuwtuwtuwtuw 3y ago
        Okay, well then this was a waste of time.
- ortichic 3y ago
  they talk about storing logs and separating databases, so good question
- TheRoque 3y ago
  Yep, I'm wondering the same thing. It seems easy to brag about using only one binary if you don't need to use another service e.g. a database.
iamcalledrob 3y ago
This is such a fantastic benefit of Golang: spin up a VPS, apply some sensible defaults, cross compile then run your binary. Compare this to deploying python, node or php... Needless complexity. If only running (and keeping running) a database server could be this straightforward!
- binarymax 3y ago
  Nowadays you can bundle a node app as a single binary file. It’s an underused feature, maybe it will catch on.
  - enva2712 3y ago
    I saw that deno did this but cool to see node picked it up too. I wish there was an option to run turbofan at build to generate the instructions rather than shipping the entire engine, but i guess that would require static deps and no eval, which can’t really be statically checked with certainty
    - binarymax 3y ago
      The engine is actually pretty small. Something like 50-100MB if memory serves (when I was using pkg)
  - dgellow 3y ago
    Could you share how that can be done? I spent some time this year trying to pack a node tool into a single fat binary for a specific use case where we wanted a history of versioned executables - i.e a build job that needs to run specific versions of the packed tool in a specific order determined by external factors. I tried Vercel pkg, Vercel ncc, nexe, and a few other tools I can’t remember right now. They all had issues with node v20, some dependencies, or seemed to not be maintained anymore. I ended up relying on esbuild as a compromise to get a fat script containing all sources and dependencies, tarballed with some static files we rely upon we can at least get versioned, reproducible runs (modulo the node env). Still not perfect, a single binary would be preferable

tuwtuwtuwtuw 3y ago

I don't use TablePlus myself. Are they talking about their marketing website? If so, then obviously thet wouldn't need to use Kubernetes. Are they talking about their application then I wonder how there can be no dependencies - don't it store data, log things, etc?

tux3 3y ago
You can store data by connecting to a database, and you can store logs by either sending them to the system journal and having a daemon collect them, or sending them to whatever cloud you like using a logging library. It's fine, really. Those database and logging services you can put in a docker if you like, but if you put them anywhere else it works just the same. A Postgres in k8s or a Postgres on a dedicated server is the same as far as the client is concerned.
- tuwtuwtuwtuw 3y ago
  But isn't that software you download and run in your own environment? I'm mostly not following what is under a DDoS attack. Is it their web page mostly consisting of marketing material with static pages?
  - gnuvince 3y ago
    > I'm mostly not following what is under a DDoS attack. Is it their web page mostly consisting of marketing material with static pages? Yes.
    - tuwtuwtuwtuw 3y ago
      Okay, well then this was a waste of time.
ortichic 3y ago
they talk about storing logs and separating databases, so good question
TheRoque 3y ago
Yep, I'm wondering the same thing. It seems easy to brag about using only one binary if you don't need to use another service e.g. a database.

iamcalledrob 3y ago

This is such a fantastic benefit of Golang: spin up a VPS, apply some sensible defaults, cross compile then run your binary. Compare this to deploying python, node or php... Needless complexity. If only running (and keeping running) a database server could be this straightforward!

binarymax 3y ago
Nowadays you can bundle a node app as a single binary file. It’s an underused feature, maybe it will catch on.
- enva2712 3y ago
  I saw that deno did this but cool to see node picked it up too. I wish there was an option to run turbofan at build to generate the instructions rather than shipping the entire engine, but i guess that would require static deps and no eval, which can’t really be statically checked with certainty
  - binarymax 3y ago
    The engine is actually pretty small. Something like 50-100MB if memory serves (when I was using pkg)
- dgellow 3y ago
  Could you share how that can be done? I spent some time this year trying to pack a node tool into a single fat binary for a specific use case where we wanted a history of versioned executables - i.e a build job that needs to run specific versions of the packed tool in a specific order determined by external factors. I tried Vercel pkg, Vercel ncc, nexe, and a few other tools I can’t remember right now. They all had issues with node v20, some dependencies, or seemed to not be maintained anymore. I ended up relying on esbuild as a compromise to get a fat script containing all sources and dependencies, tarballed with some static files we rely upon we can at least get versioned, reproducible runs (modulo the node env). Still not perfect, a single binary would be preferable