4 ms·
Note that my only complaint is terminological, because I think "function call" signifies something completely different from "launching a long-lasting service".
by mbrock 10y ago
Note that my only complaint is terminological, because I think "function call" signifies something completely different from "launching a long-lasting service".
- jdmichal 10y agoYes. If starting a Docker instance is a "function call", then what is the analog for making a HTTP request to a Docker-hosted server? The analogy was fine for describing the idea, and perhaps it even holds if the Docker image is a processing step instead of a service. But if the Docker image is a service... We have a set of terminology (and technology!) already for services -- let's use those, rather than continue to force the analogy all the way down.
- monkmartinez 10y agoNoted. I think the intent is there... treat/use/consume containers like parts of your app. Ie. Call the DB container, do work, release the DB container, and so on. Not a completely separate "thing" that is a PITA to debug, prone to errors, and horrifically documented. Why can't my app's ORM function call the DB container and do stuff? Why do I have to wire them up twice (code and OS layer) or more?