4 ms·

A tale of two projects: One one project (RoR), I have a BIG-IP load balancer in front of 4 dedicated servers, one of which is a db. On another project, I am r

• sanswork 17y ago
  The one where you haven't outsourced the server support? Thats not a win for GAE so much as it is for outsourcing your server support.
  • thetrumanshow 17y ago
    Oh, I see. Then, guess which one doesn't require me to seek out and contract a firm to handle my admin for me?
    • sanswork 17y ago
      The self managed RoR one. For the GAE one you sought out someone to host and manage your servers for you and contracted Google to do so.
      • thetrumanshow 17y ago
        Well, technically, both have some level of management which is bundled with the services. Ex: I don't have to literally put out fires if one breaks out in the server room. App Engine's management service by contrast is very tightly bundled to the hosting services... so tightly in fact that the cost of the management service they provide is exactly proportional to the cost of the resources I consume. It's a great deal. But we are getting off into the weeds here. App Engine simplifies server admin for me. I have never had to personally 'bounce' anything for any reason. I don't worry about running out of disk space. I don't have to worry about sweeping out the sessions (on disk or db). I don't have to setup database replication. I don't have to configure rolling archive tables to improve the speed of access to the most commonly accessed data on a large table. Being a solo operation, App Engine is ideal.