cloudfoundry - What is the difference between Cloud Foundry and Docker? -

i java developer. use weblogic host our applications. have been told replacing weblogic opensource alternative. planning use springboot. looking @ docker/cloud foundry. docker/cloud foundry new territory me.

1. can please tell me difference between cloud foundry , docker?
2. if use docker not cloud foundry, missing out on?
3. if use cloud foundry not docker, missing out on?

thank help.

docker technology creating , running linux "containers." in sense, can think of these lightweight vms. docker container springboot app consist of docker image, contain filesystem things needed run app (jvm, source code, etc.), , docker container metadata, tells docker daemon how run app inside image (e.g. environment variables set, ports expose, commands run, etc.). docker daemon use linux features such cgroups , kernel namespaces run container in isolation other processes running on host machine. docker low-level, in need specify goes image, , runs arbitrary things, namely whatever put image , tell run. docker container portable, can build, test, , run docker container locally development, , ship container production host has docker daemon running on it, , quite confident you're getting exact same thing.

cloud foundry works @ higher layer of abstraction, applications being first class concept. cloud foundry uses containerization technology similar docker build portable images , run them, it's implementation detail , don't need specify details. in newer versions of cloud foundry, docker images supported can specify details if want, has "buildpack" workflow, automatically detect java application when push app , know include things necessary java runtime when builds image.

with cloud foundry, since applications , application management first class concepts, , since operates @ higher level, sorts of things free. instance, can scale app horizontally (add instances), e.g. cf scale my_app -i 5 or vertically, cf scale my_app -m 2g (to set allocated memory each instance). streaming application logs: cf logs my_app. cloud foundry gives lot of fault tolerance free, if 1 of application instances crashes, or process running application containers crashes (the thing that's similar docker daemon), or if host vm that's running container-running process dies, or hardware cluster vm resides dies, cloud foundry automatically bring instances up.

the docker daemon single process can run on linux machine. if you're doing small , simple, , need of setup yourself, can easier , running both locally , in development using docker. docker it's easier have access , share docker image create, once you've created image, can put in docker repository, , can run on other docker daemon. cloud foundry, built image implementation detail , don't have access it, instance couldn't extract image , run on cloud foundry installation.

there various projects out there intended make cloud foundry more accessible , easier set up, while still giving many of benefits of paas. of these projects aim allow combine using docker , benefits of docker while getting lot of paas benefits cloud foundry.

see lattice , cloud foundry on bosh-lite.

there several hosted cloud foundry services.

see pivotal web services , ibm bluemix

there lot of non-cf projects intended put platform layer around core docker technology, in both run-your-own , hosted-service varieties.

see google's kubernetes project , amazon container service

full disclosure: i'm software engineer working on cloud foundry @ pivotal