4 ms·

A rocket lands like it's done it 1000 times from space, and my company can't even code a simple microservice or use containers.

by jjm 11y ago

deegles 11y ago
To be fair, I doubt the rocket is running microservices either :)
- noselasd 11y ago
  Embedded systems like this is normally coded (on top of an RTOS) as individual services each running on one thread exchanging messages with other services. Pretty much like microservices (just not over http) (Take a look at e.g. http://flightsoftware.jhuapl.edu/files/2012/FSW12_McComas.pdf http://flightsoftware.jhuapl.edu/files/2012/FSW12_McComas.pd... which is NASAs approach to reusing the typical architecture for flight software)
  - yetihehe 11y ago
    So like a small version of erlang? Once you've started programming in erlang you start to look at concurrency and reliability in a certain way. Especially after you've done some server which took too many hours to stop hanging and crashing on interthread issues.
joshontheweb 11y ago
Lol. I catch myself chastising myself often around SpaceX launches. They are launching rockets faster than I can get my SaaS launched out of Beta!?!
imaginenore 11y ago
I get why companies with huge infrastructure use containers, the efficient spread of resources. I absolutely do not get why an average web app running on a few servers would use them.
- jjm 11y ago
  Edit: my reasons look so small compared to that rocket landing. Makes me feel like whatever I'm working on is just _not_ BIG enough. Rolling upgrades, artifact transport, and cleaner host machine alone can give you extra donut and YouTube time. Also doing forensics can be easier knowing the a specific container is at fault. About the clean base host, One doesnt have to install anything really. No worries about runtimes, supporting libs, etc. This allows new machines to start even faster from zero. More donut and YouTube time.
  - imaginenore 11y ago
    All of that can be done with simple shell scripts and chroot jails on bare metal. Also I don't see how it eliminates runtimes and libraries.
    - jjm 11y ago
      Doesn't eliminate them, but as a sysadmin doesn't have to worry about what version of it or even if runtimes such as ruby/Java/Python exist, any devel libs, exist in the machine. That same container can move from my desktop to any environment.

A rocket lands like it's done it 1000 times from space, and my company can't even code a simple microservice or use containers.

by jjm 11y ago

A rocket lands like it's done it 1000 times from space, and my company can't even code a simple microservice or use containers.

deegles 11y ago

To be fair, I doubt the rocket is running microservices either :)

noselasd 11y ago
Embedded systems like this is normally coded (on top of an RTOS) as individual services each running on one thread exchanging messages with other services. Pretty much like microservices (just not over http) (Take a look at e.g. http://flightsoftware.jhuapl.edu/files/2012/FSW12_McComas.pdf http://flightsoftware.jhuapl.edu/files/2012/FSW12_McComas.pd... which is NASAs approach to reusing the typical architecture for flight software)
- yetihehe 11y ago
  So like a small version of erlang? Once you've started programming in erlang you start to look at concurrency and reliability in a certain way. Especially after you've done some server which took too many hours to stop hanging and crashing on interthread issues.

joshontheweb 11y ago

Lol. I catch myself chastising myself often around SpaceX launches. They are launching rockets faster than I can get my SaaS launched out of Beta!?!

imaginenore 11y ago

I get why companies with huge infrastructure use containers, the efficient spread of resources. I absolutely do not get why an average web app running on a few servers would use them.

jjm 11y ago
Edit: my reasons look so small compared to that rocket landing. Makes me feel like whatever I'm working on is just _not_ BIG enough. Rolling upgrades, artifact transport, and cleaner host machine alone can give you extra donut and YouTube time. Also doing forensics can be easier knowing the a specific container is at fault. About the clean base host, One doesnt have to install anything really. No worries about runtimes, supporting libs, etc. This allows new machines to start even faster from zero. More donut and YouTube time.
- imaginenore 11y ago
  All of that can be done with simple shell scripts and chroot jails on bare metal. Also I don't see how it eliminates runtimes and libraries.
  - jjm 11y ago
    Doesn't eliminate them, but as a sysadmin doesn't have to worry about what version of it or even if runtimes such as ruby/Java/Python exist, any devel libs, exist in the machine. That same container can move from my desktop to any environment.