Saturday, October 25, 2014
Detecting SSL in PHP on Heroku
Sunday, June 29, 2014
PaaS: Google AppEngine v.s. Heroku
Reference
- http://www.scriptrock.com/articles/heroku-appengine
- https://news.ycombinator.com/item?id=4573685
- http://kmilo0.blogspot.tw/2013/02/gae-vs-heroku.html
Intro
Comparison
Language Support
Heroku: Ruby, Java, Node.js, Python, PHP, Clojure, Scala / PostgreSQL, MongoDB, Cloudant, Redis
Comments for Google AppEngine
AppEngine’s proprietary, read-only nature results in tedious and unnecessary code refactoring; apps have to be written specifically with AppEngine in mind, API’s have to be written specifically for AppEngine, even standard Java code has to be extensively altered to fit into the AppEngine environment.
Google insists on AppEngine customers only using its BigTable non-relational database, although they have also recently added some support for CloudSQL.
Comments for Heroku
Heroku’s database-platform choices reflect a collection that is in widespread use already in the wider world.
Comments on Both
Heroku’s database-platform choices reflect a collection that is in widespread use already in the wider world.
My Summary
IaaS, PaaS, SaaS
Intro
SaaS: Software as a Service
Examples
- Gmail
- Google+
PaaS: Platform as a Service
One can develop applications and let them execute on top of the platform which take care of the execution.
Vendors manage:
- runtime
- middleware
- O/S
- virtualizatoin
- server
- storage
- networking
Users manage:
- application
- data
Examples
- Heroku
- Google App Engine
IaaS: Infrastructure as a Service
Users buy fully outsource service (the whole virtual machine)
Examples
- AWS(Amazon Web Services)
- Linode