ENTRYPOINT and CMD confusion in a nutshell exec form (json form) and shell form in brief exec: [run.sh] => run.sh (command must be in $path ) shell: run.sh => /bin/sh -c run.sh ENTRYPOINT exec form [run.sh] execute whatever written, subsequent keywords become params to this executable => run.sh ENTRYPOINT shell from run.sh execute the script with prefixing with /bin/sh -c. so it becomes => /bin/sh -c run.sh CMD if there is an ENTRYPOINT defined then this CMD become parameter only. unless ENTRYPOINT defined as shell from which makes CMD ignored. no ENTRYPOINT + CMD [run.sh hello] => /bin/sh -c run.sh hello ENTRYPOINT shell form run.sh hello + CMD exec/shell from => /run.sh (be careful the this command is in the path location ) (notice that CMD is ignoed in this case) ENTRYPOINT exec form [run.sh, hello] + CMD exec form [run.sh ,hello2] => run.sh hello run.sh hello2 (notice that second run.sh is a param only) ENTRYPOIN...
functional reactive programming, particularly rxjava2 in this post, is really fun when get accustomed to but getting familiar and thinking in reactive way is a little hard as first days. anyway, after several days of reading then I have implemented this style in one of my commercial projects. this paradigm save us lots of hardware resource also happy customers who apply our interface which observe the events triggered by this apply by customer. honestly speaking, due to well designed implementations, we have not faced any threshold issue but to be ready those issues beforehand, I started curious about thread pools and management. observeon and subscribeon are two ways to manage these thread pool either self constructed by Schedulers.from() or one of prebuild Schedulers in the framework. real reason I want to deeply analyse this is, names of those two operations are misleading at first interaction. not sure they will come true for me when I work more with Rx frameworks. I th...