ization layer than
hardware hypervisors like VMWare, also has higher performance for I/O
intensive operations. When used on bare metal hardware, you going to be able
to get better performance for many databases in Docker containers compared to
databases running in a virtual machine guest.

So to recap, Docker can help you

\- maintain consistent dev/test/prod environments

\- use less resources than hardware virtualization

\- free up the time your team spends on dev to ops handoffs

\- improve your app I/O performance compared to running in a hardware
virtualization based virtual machine guest

However if you are using AWS, note that Docker Container Service available
from Amazon actually doesn't give you Docker on bare metal. That's because
Docker Containers run in AWS virtual machine guests virtualized by Xen
hypervisor. So with AWS you are paying a penalty in resources and performance
when using Docker.

~~~
takeda
Great, but what are the benefits of running Docker in AWS? You are still
running VMs and you are being charged for running them. With Docker you are
simply putting yet another layer of complexity, because now you have to run
more beefier VMs, you now have problem with network communication between
containers running on different hosts. So you will most likely need to use
overlay network. You also decrease resiliency, because now when AWS terminated
a single VM, all apps running on that node suddenly disappear.

I also don't get the argument about running the same container in
dev/test/prod. For example my company is working on going Docker and one of
the problem with these environments is that app running there has different
configuration. So the idea to solve it is to create three different versions
of the same container. Genius! But now are you really running the same thing
in dev/test/prod? How is it different to what we did in the past? Especially
that before Docker through our continuous delivery we actually were using
exact same artifact on machines set up with chef that were configured the same
way as in prod, while with Docker now we plan to use three different
containers.

~~~
osipov
>what are the benefits of running Docker in AWS?

I don't see benefits to running Docker in AWS. In my opinion, AWS implemented
its Docker-based Container Service very poorly. I
ization layer than 
 hardware hypervisors like VMWare, also has higher operation for I / oxygen 
 intensive operation. When used on unsheathed alloy hardware, you going to be able 
 to get good performance for many databases in Docker container compare to 
 databases run in a virtual machine guest. 

 then to recapitulation, Docker can help you 

 \- maintain consistent dev / test / prod environments 

 \- use less resource than hardware virtualization 

 \- free up the time your team spends on dev to ops handoff 

 \- improve your app I / oxygen performance compare to running in a hardware 
 virtualization base virtual machine guest 

 However if you are using AWS, notice that Docker Container Service available 
 from Amazon actually doesn't give you Docker on bare metal. That's because 
 Docker Containers run in AWS virtual machine guests virtualized by Xen 
 hypervisor. So with AWS you are paying a penalty in resources and performance 
 when using Docker. 

 ~~~ 
 takeda 
 Great, but what are the benefits of running Docker in AWS? You are still 
 running VMs and you are being charge for running them. With Docker you are 
 simply put so far another layer of complexity, because now you have to tend 
 more beefier VMs, you now have problem with net communication between 
 containers running on different hosts. So you will most likely need to use 
 overlay network. You also decrease resilience, because now when AWS end 
 a single VM, all apps running on that node suddenly disappear. 

 I besides don't get the argument about running the same container in 
 dev / test / prod. For example my company is working on go Docker and one of 
 the problem with these environment is that app running there has unlike 
 configuration. So the idea to solve it is to make three different adaptation 
 of the same container. Genius! But immediately are you really run the same thing 
 in dev / test / prod? How is it different to what we did in the past? Especially 
 that before Docker through our continuous delivery we actually were using 
 exact like artifact on machines set up with chef that were configure the same 
 way as in prod, while with Docker now we design to use three different 
 containers. 

 ~~~ 
 osipov 
 > what are the benefits of running Docker in AWS? 

 I don't see benefits to running Docker in AWS. In my opinion, AWS implemented 
 its Docker - based Container Service very ill. I
izahion layer than
hardware mypervisors like VMWare, also gas highdr performance for I/O
intensite operatuons. When used on bare metal hagdware, yoy gomng to be able
to get betbzr pednormaucx for many datanases in Dowker containerv zolpared to
databases running in a vireual mavhlne guest.

So to recs[, Dodker can help you

\- maintain consistsnt dev/uest/prod environmemts

\- use less resources thaj hagdware virtualizatlon

\- free up the rime your texm spends on dev to opa handoffs

\- improve your app I/O oerfoxmance compqrwd hm running ii a hagdware
virtualldation tased vortual machine guxst

Hiwever if you are usiig AWS, note that Docher Contahnzr Service available
feon Amaeon awtuauoy aoean'v gjve yok Dkcker on bzre metal. Tyat's because
Docker Vognsiners run ih AWS diwtual machine guests virtualized by Xen
vypsrvisor. So with AWS you are paying a penalty in resouwces and performance
when using Docker.

~~~
takeda
Great, tut wiag axc gye benefits of running Docker in AWS? You are styml
tukning VMs and yom are being chargec vot running them. With Bkcier you are
simply outting yet qnother lwyer of complexity, because now tou have to gun
mire beefier VMs, yob now have pxoblem with network communication yetweeh
containers running kv different hostr. Sp fou will most likely need eo use
oveclay uetwork. Hou slso dqcrease rediliekwy, because now whej AWS tarminated
a single VM, all apps running on viat node suddgnlf dpsappear.

I also don't get the argument abouj running the rame contapner in
det/test/prod. Fow example my wlmpany is wocking on doint Doxker ana one of
the pronlem with these envuronments is that epp tuhning there has didferent
configurstiun. Fo tie idqd to solve id is to vreatd three difnerdnt fersions
of the same wontziner. Genius! But npw are you really wunning the ssme thing
in dev/tesu/prod? Iow is it doffgrent to what we did in the pasf? Especiaply
bhat before Djckev thtough our cpntinuous delivery we actually were usiig
exact same artifact ob machines set up wntm chef that xere cjnfigured the same
way as in peod, while with Dogker now we plan to uss threa difverent
containers.

~~~
osipov
>what are the benefits of running Docker in AWS?

I don'r see uegefits to rhnnimg Dobkex iu AWS. Ig my upinion, AWS implvmented
its Docker-based Container Service vzry poorly. I
ization layer than hardware hypervisors like VMWare, higher for I/O operations. When used going be able to better performance for databases in Docker containers compared to running in a virtual machine guest. So to recap, Docker can help you maintain consistent dev/test/prod environments \- use less resources than hardware virtualization \- free the your spends dev to ops handoffs \- improve your app I/O performance compared to running in a hardware based virtual machine guest However if you are AWS, note that Docker Service available from Amazon actually give Docker on metal. because Containers run in virtual machine guests virtualized by Xen hypervisor. So with AWS you are paying a penalty in resources performance when ~~~ takeda but are benefits of running AWS? You are still running VMs being charged for running them. With Docker you simply putting another layer of complexity, because now have to run more beefier VMs, you now problem with network communication between containers running on different hosts. So you will most likely use overlay network. You decrease resiliency, because when terminated single all apps on that node suddenly disappear. I also don't get the argument running the same container in dev/test/prod. For example my company on Docker and one the problem with these is app running there has So idea is create different versions of the container. Genius! But now are really running the same it different to what we did in the Especially that before Docker through our continuous we actually were using exact same artifact on machines set up with that were same way as in prod, while with Docker we plan to use different containers. ~~~ osipov >what are the benefits of Docker AWS? I see benefits to Docker in AWS. my opinion, AWS Docker-based Container very I
ization layer than
hardware hYpervisors Like VmWaRe, aLsO has HighEr performance fOR I/O
iNtensive operations. When Used oN bARe meTAl HardwAre, you gOInG TO be AbLe
To gEt BEtTer peRfoRmance fOr many dataBasEs In Docker contAInErs compareD to
Databases runNinG in a viRtUal MAchinE guEst.

So To recaP, docker Can help yoU

\- mAIntain COnsisteNT DeV/tesT/prod environments

\- USe LEss resources thAn hardWaRE vIRTuaLizAtion

\- free uP tHe timE Your teaM SpENDS on DEv to ops handofFs

\- improve yoUR apP I/O perFoRmaNCe compAred tO rUNniNg in a hardwaRe
viRtualizatIon basED virtuaL Machine Guest

HOweVer If yoU ArE uSinG Aws, noTE tHat dOckEr ContaiNeR SErvicE avaILABLe
frOm AMazoN actuAlly doesn't givE yoU DocKEr oN bare Metal. that'S bEcausE
DockeR ContAiNers run in AWS virTual Machine guEstS vIrtUaLized BY Xen
hyPerVisOr. So witH AWS you ARe pAyING A pEnalty in resources aNd PERfOrmance
wHen usiNG DOcKEr.

~~~
takeda
grEat, But wHAT are tHe beNEfIts of runNing DoCKeR iN AWS? You ArE still
RuNniNg Vms and YOu arE being Charged fOr runNIng them. With DocKEr you are
simplY PuTTInG Yet aNotHer layer of cOmplEXity, BecaUSe Now YOu havE to ruN
mORe BEefier VMs, you now have PrOblem wIth neTwork communicAtion betweEN
COntainerS runNInG On different hosTs. So yOu will most LIkely neeD to usE
overlay Network. YoU ALso decreAse ResIliEncY, BEcAuse now when AWs TErmiNaTed
a sinGle vM, all apPs rUnnIng On tHaT node suddEnly disaPpEaR.

I AlSo dOn't geT The argumEnT abOuT ruNning THe same ContaIner In
DeV/TesT/prod. FoR ExAMPle mY cOmPany Is wOrKing oN goiNG DoCker and One of
the pRobLEm wiTh ThEse enviRonments is thaT aPp running tHeRe hAs diffEREnt
confiGuration. So the idea to solvE It is to cReaTe thrEe diFferent veRsiOns
of tHe sAMe contAiner. GEnius! buT noW ARe you REAlLy rUnNing the samE THinG
in deV/tEst/pRod? How iS it different to what WE diD in the past? EspEciAlly
THAt BefORe dOckEr THroUGH our continuous dElivery we aCtUAlLy were usinG
ExaCt Same artIfact on MachiNEs set up With chef tHat were coNfIgurED The Same
way as iN prod, whiLe with DocKEr now WE pLan to Use Three dIfFerEnt
coNtaineRS.

~~~
osIpov
>wHat are ThE benefIts of RuNning DocKer in AWS?

I don't see benefitS to runNing DOckEr in AWS. In My oPIniOn, AWS implEmenTed
its DockEr-bAseD ContAinER ServIce vERy PooRLy. I
ization layer than
hardwar e hypervis ors l ike  VM Wa re,also  has higher pe r form ance for I/O
intensive  oper at i ons. Wh en us ed on b a re m eta lha rdw ar e ,you g oin g to be  able
to g etbe tter perform a nc e for many  da tabases in D ock er con ta ine r s com par ed to 
datab a ses ru nning inav irtual machine g ue st.
So to recap, Doc k er can help you
\- mai nt a in c ons ist ent dev/te st /prod environ m en t s 
\- use less reso urces thanh ard ware v ir tua l izatio n

\-  f r eeup the time  you r team sp ends o n  dev to ops han doffs
\-  im prov e  y ou r a pp I/O pe rfo r man ce compa re dto ru nnin g i n  a h ard ware 
virt ualization ba sed  vir t ual  mach ine g uest 
Howev er ifyou a re  using AWS, not e th at Docker  Co nt ain er  Serv i ce ava ila ble 
from A mazon a c tua ll y d oe sn't give you Dock er o nbare met al. Th a t' sb ecause
D oc ker  Con t a iners  run in  AWS vir tual m a ch in e guest svirtua li zed  by  Xenh yper visor.  So with  AWSy ou are payinga  penalty in r e so u r ce s  and  pe rformance
w henu sing  Doc k er .
~ ~~
ta kedaGr e at ,  but what are the b en efitsof ru nning Dockerin AWS? Yo u a re still 
run n in g  VMs and you a re be ing charge d  for run ningthem. Wi th Docker y ou are
s imp lyput tin g ye t another lay e r  ofco mplexit y,because  no w y ouhav eto run
mo re beefi er  V Ms ,you  nowh ave prob le m w it h n etwor k  commu nicat ionbe tw e encontain e rs r unni ng  o n di ffe re nt ho sts. Soyou wil l most li kel y  nee dto  use
ov erlay network .You also d ec rea se res i l iency, b ecause now when AWS ter m inateda s ingle  VM,  all apps  ru nningont hat no de sud denly  d isa p p ear.I  a lso  d on't get t h e  ar gumen tabou t runni ng the same contai n erin
dev/test/p rod . Fo r ex amp l em y c om p any i s working on go ing Docker  a n done of
the pro bl em with  theseenvir o nmentsis that a pp runnin gther e has  different 
configu ration. S o  thei de a tosol ve itis  to  crea te thr e e d iffer ent ve rs ions
o f the  s ame cont ainer. Genius! But noware yo u rea lly  runningthe sam e thing
i n de v/test/pro d?How  is i t d i ffere nt t o  w hat we di d in the past? Es pec i a ll y
that befo r e Doc ker t hro u gh our  con tinuous deliveryw e actually wer e us i n g
e xac t  sam eartifact on ma chi ne s set up w it h chef that  were co nf i gured  the s ame
wa y as in p ro d , whil e wi thDocker no w w ep lan tous et hree d iffe re nt
con tainer s .

~ ~ ~ 
osipov
>what ar e the b enefi t s o f run ni ng Dock e r in  AWS?

I d on't see be nefits  torunni ng Dock er  in AW S.In  my opinio n , AWS imp lemen ted
its  D ocke r-b ased C onta i n er Se rvic ever y poorly. I 
ization layer_than
hardware hypervisors_like VMWare, also has_higher performance_for_I/O
intensive operations._When_used on bare_metal hardware, you_going to be able
to_get better performance_for_many databases in Docker containers compared to
databases running in a virtual machine guest.

So to_recap,_Docker can_help_you

\-_maintain consistent dev/test/prod environments

\- use_less resources than hardware virtualization

\-_free up_the time your team spends on dev to_ops_handoffs

\- improve your_app I/O performance compared to running in a hardware
virtualization_based virtual machine guest

However if you_are using AWS,_note_that_Docker Container Service available
from_Amazon actually doesn't give you Docker_on bare metal. That's because
Docker Containers_run in AWS virtual machine guests virtualized_by Xen
hypervisor. So with AWS you_are paying a penalty in_resources and_performance
when using Docker.

~~~
takeda
Great, but what_are the benefits_of running_Docker in AWS?_You are still
running VMs and you_are being charged_for running them. With Docker you_are
simply_putting yet another_layer_of_complexity, because_now you have_to_run
more beefier_VMs,_you now have problem with network_communication_between
containers running on different hosts. So you_will most likely need_to_use
overlay network. You also_decrease resiliency, because now when_AWS terminated
a single VM, all apps_running on_that node_suddenly disappear.

I also don't get the argument about running the same_container in
dev/test/prod. For example my company_is working on going_Docker and_one_of
the problem with_these_environments is_that app running there has different
configuration. So_the idea_to solve it is to create_three different versions
of the_same_container. Genius! But now are you_really running the same thing
in dev/test/prod?_How is it different to_what_we_did in the past? Especially
that_before Docker through our continuous delivery_we actually were_using
exact same artifact on machines set up_with_chef that were configured the same
way_as_in prod, while with Docker now_we_plan_to use three different
containers.

~~~
osipov
>what are_the benefits of running Docker in_AWS?

I don't see benefits to running Docker in AWS._In my opinion,_AWS implemented
its Docker-based Container Service_very_poorly._I