"Containers" has come to be a deeply overloaded term, and I see it causing confusion nearly every day. There are at least four things here.
-
-
The design philosophy is as applicable to instances, and mostly to functions, as it is to containers.
Prikaži ovu nit -
I don't have alternative terminology to propose, but I think it would simplify a lot of conversations if people were more clear about which of these (or other things) they are talking about.
Prikaži ovu nit
Kraj razgovora
Novi razgovor -
-
-
While I agree with all your points, we don't always need all four properties when using containers(!), static linking... is not a solution. I mean, it might be if you're writing C or Rust with no config or other assets. But it's very difficult for languages like Python.
-
For sure. Containers-as-packaging are really convenient and powerful for stuff like this, just not the only game in town.
Kraj razgovora
Novi razgovor -
-
-
I got lost in a sea of confusion for a long time. Then I began to think of containers as strengthened processes, not lightweight VMs.
- Još 1 odgovor
Novi razgovor -
-
-
There's also the aspect of scale - Do you see a convergence with HPC 'infra design patterns'? The 'hard' differences seem to be loose-coupling/isolation between processes (cloud/faas) vs. hard-coupling (hpc/MPI)
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.