(codesandbox.io)

169 points hunvreus | 1 comments | 08 Apr 25 14:55 UTC | HN request time: 0.215s | source

Show context

1970-01-01 ◴[11 Apr 25 13:45 UTC] No.43653731[source]▶

The VM vs container debate is fascinating. They are separate yet slowly merging concepts that are becoming more blurred as technology becomes cheaper and faster. If the real bottleneck to scale is adaptable code, then it is foolish to dismiss the VM as outdated tech when it can be completely rehomed in 2 seconds. That megabyte of python code managing your containers would still be busy checking it's dependencies in that same timeframe.

replies(2): >>43655040 #>>43662605 #

1. znpy ◴[11 Apr 25 15:34 UTC] No.43655040[source]▶

>>43653731 #

In a way it's nothing new. MOSIX/openMosix (https://en.wikipedia.org/wiki/MOSIX, https://en.wikipedia.org/wiki/OpenMosix) did similar stuff with individual processes. It would probably be even faster as then you would have to only move process memory and its state rather than the whole VM memory (and it state).

I guess it would/could be nice to have something that moves kubernetes pods around rather killing them and starting new ones.

↑

We clone a running VM in 2 seconds (2022)