Java PaaS shootout , Java Paas 논쟁: Google App Engine, Amazon Elastic Beanstalk, CloudBee를 비교
Google GAE, Amazon Beanstalk, VMware Cloud Foundry, and Cloud Bees 비교
GAE : 제약된 Java, RDB 보다는 NoSql에 초점 response time 제약등
Amazon Beanstalk : Amazon infra사용. Auto-scaling. US EAST에서만 사용가능. Tomcat, VM에 대한 detail control가능.
Eclipse plugin 존재. Virtual Access Cloud. Tomcat + RDBMS
1 server = 1 VM
CloudFoundry : PHP, Erlang, Python 지원은 커뮤니티에서 개발함
NO elastic scaling
easy to create your own elastic scaling
http://www.slideshare.net/cobiacomm/introduction-topaa-s http://blog.cobia.net/cobiacomm/2011/11/02/paas-evaluation-framework-for-cios-and-architects/
http://crackradio.com/post/19884367834/paas : Heroku, Cloudfoundry, dotCloud 비교Open Paas 비교 자료 : http://blog.daum.net/htann/41http://www.virtualizationpractice.com/vmwares-cloudfoundry-and-red-hats-openshift-compare-and-contrast-10567/[http://www.virtualizationpractice.com/vmwares-cloudfoundry-and-red-hats-openshift-compare-and-contrast-10567/]http://www.aircondream.co.kr/
Heroku의 오픈소스판 비슷 :http://nodester.com/
Kernel component : Router ,CloudController, DEA(Droplet Execution Agent), HealthManager ,ServiceProvisioningAgent ,MessagingSystem vSphere, OpenStack, AWS, MicroCloud 다 가능.. Juju + Cloudfoundry : http://www.cloudave.com/14950/ubuntu-ensemble-is-now-juju/
-
http://www.activestate.com/blog/2014/04/docker-and-cloud-foundry
-
Decker : DEA의 API를 구현
-
Stackato
-
Diego : DEA대체
-