3 ms·

Don’t come here speaking sense against a decade of marketing! Realistically I wish someone would just write an orchestrator that runs Go processes and nginx an

by hughrr 5y ago

Don’t come here speaking sense against a decade of marketing! Realistically I wish someone would just write an orchestrator that runs Go processes and nginx and glues it all together.

forty 5y ago
Can't a container mostly be a Go process? "Marketing" as you said, made this concept of "container", but I think using the words "process" and "namespaces" is still ok.
- hdjjhhvvhga 5y ago
  I don't agree "container" is marketing-speak; you could say it was appropriated, but I was using linux-containers in early 2000s when it was still a kernel patch. We all knew that bare metal offers a lot and our servers are underutilized most of the time, and VMs were considered a heavier option.
  - forty 5y ago
    I still think using "container" lose the fact that it's just a process with some tweaks :) I'm not saying "marketing" as to say it was coined by non technical people, but rather that it's a way to "sell" the feature. Like you go see your manager and say "I'm going to containerize the application" vs saying "I'm going to add some isolation settings to the process"
cyberge99 5y ago
Consul and nomad would like a word with you.
- hughrr 5y ago
  See my post history. No thanks :) https://news.ycombinator.com/item?id=30020427 https://news.ycombinator.com/item?id=30020427
kcartlidge 5y ago
> Realistically I wish someone would just write an orchestrator that runs Go processes and nginx and glues it all together. Not quite what you're asking for but you can get close, on bare metal, with: - ssh to set up a systemd service, scp to deploy your binary, then ssh again to restart your service - dokku (containers are optional) with its cli For the first option, once you've set up nginx on the server you can easily automate the addition of a new systemd service for a new app with a simple shell script. That done, it is a matter of less than a minute to add a new app and even quicker to update and restart an existing one. For the second option, it is installed with a single bash command and supports Heroku build packs which means for many systems there's virtually (or exactly) no config needed. Just run the cli from within your app folder. If you do want containers they are automatically found and deployed too. I've done most deployment methods from the simplest (above) through to complete Terraform builds, and once they are automated all that matters is that the method you choose supports your needs. Go for the simplest option that does that.

by hughrr 5y ago

Don’t come here speaking sense against a decade of marketing! Realistically I wish someone would just write an orchestrator that runs Go processes and nginx and glues it all together.

forty 5y ago

Can't a container mostly be a Go process? "Marketing" as you said, made this concept of "container", but I think using the words "process" and "namespaces" is still ok.

hdjjhhvvhga 5y ago
I don't agree "container" is marketing-speak; you could say it was appropriated, but I was using linux-containers in early 2000s when it was still a kernel patch. We all knew that bare metal offers a lot and our servers are underutilized most of the time, and VMs were considered a heavier option.
- forty 5y ago
  I still think using "container" lose the fact that it's just a process with some tweaks :) I'm not saying "marketing" as to say it was coined by non technical people, but rather that it's a way to "sell" the feature. Like you go see your manager and say "I'm going to containerize the application" vs saying "I'm going to add some isolation settings to the process"

cyberge99 5y ago

Consul and nomad would like a word with you.

hughrr 5y ago
See my post history. No thanks :) https://news.ycombinator.com/item?id=30020427 https://news.ycombinator.com/item?id=30020427

kcartlidge 5y ago

> Realistically I wish someone would just write an orchestrator that runs Go processes and nginx and glues it all together. Not quite what you're asking for but you can get close, on bare metal, with: - ssh to set up a systemd service, scp to deploy your binary, then ssh again to restart your service - dokku (containers are optional) with its cli For the first option, once you've set up nginx on the server you can easily automate the addition of a new systemd service for a new app with a simple shell script. That done, it is a matter of less than a minute to add a new app and even quicker to update and restart an existing one. For the second option, it is installed with a single bash command and supports Heroku build packs which means for many systems there's virtually (or exactly) no config needed. Just run the cli from within your app folder. If you do want containers they are automatically found and deployed too. I've done most deployment methods from the simplest (above) through to complete Terraform builds, and once they are automated all that matters is that the method you choose supports your needs. Go for the simplest option that does that.