developing on GAE introduced such design complexity that working around it pushes us 5 months behind schedule. I thought that Carlos Ble's post Goodbye Google App Engine (GAE) is a good example that illustrates why the initial perception behind GAE as a simple platform that provides extreme productivity can be completely wrong. Control tradeoffs in PaaS, I tried to outline the main limitation of most of the current "blackbox PaaS" implementations: In one of my earlier post on the subject, Productivity vs. The typical SysAdmin thinks that they can get to 75% of PaaS functionality with DevOps tools like Chef without giving up any systems architecture flexibility. SysAdmins may ask: "isn't PaaS just a monstrous black box that prevents me from provisioning the specific services we need to deploy real-world apps?".Developers may ask: "if I have a self-service portal for deploying applications (aka PaaS), do I need SysAdmins at all?".But they take a fairly different approach to deliver on that promise.Ĭhristoper Knee summarized it in his blog post DevOps and PaaS - Friend or Foe? as the difference between Developers and SysAdmin: Beatunes unable to acquire jdbc connection full#With DevOps, you get tools to automate your operational environment through scripts and recipes, and keep full visability and control over the underlying infrastructure.īoth PaaS and DevOps aim toward the same goal - reducing the complexity of managing and deploying applications on the cloud.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |