![]() Part of the reason that brought Carlos through that experience IMO is that in the course of trying to make GAE extremely productive the owner made the platform too opinionated, to the point where you lose all the potential productivity gains by trying to adopt their model. 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: 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. DevOps - DevOps takes a more operations-driven approach.The PaaS platforms deals with all the operational aspects needed to run your code such as deployment, scaling, fail-over, etc. A PaaS platform provides generic application containers to run your code. ![]() PaaS - PaaS takes a developer, application-driven approach.Krishnan represents one of the common attitudes and subjects of debate between two main paradigms for developing and managing applications on the cloud: In fact, with cloud computing, the role of the Ops is not going away but it stays in the background offering an interface which developers can manage themselves. With PaaS, organizations can keep the existing distinction between the Ops and Dev teams without worrying about the cultural change. ![]() When organizations embrace PaaS instead of infrastructure services, we don’t need the DevOps marriage and the associated cultural change (believe me, this cultural change is giving sleepless nights to many IT managers and some consultants are even making money helping organizations realize this cultural change). The shift in the thinking about the enterprise cloud consumption also poured water into the “DevOps” concept advocated by vendors and pundits with their foot in the IaaS world. The thing that caught my attention was Krishnan's comments on why PaaS is a superior alternative to DevOps: I was reading Krishnan Subramanian's post, Two Events That “Clouded” Our Thinking In 2011.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |