DevOps Zone is brought to you in partnership with:

As VP of Technology Evangelism at WSO2, Chris Haddad raises awareness of Platform as a Service, Cloud Architecture, Service Oriented Architecture, API Management, and Enterprise Integration. Prior to joining WSO2, Haddad’s experience includes building software development teams, contributing to open source, crafting technology roadmaps, leading Gartner research teams, and delivering Software as a Service and Web applications. Chris is a DZone MVB and is not an employee of DZone and has posted 111 posts at DZone. You can read more from them at their website. View Full User Profile

What is NoOps?

  • submit to reddit

Make DevOps and NoOps a cornerstone of improving your software delivery; just don’t think NoOps PaaS entirely defines ‘What is a True, Complete PaaS’.  The DevOps and NoOps movements promote quick project startup, rapid release iterations, and incremental solution testing. Lucas Carlson and Adron Hall posted a good article describing how integrating development environments with runtime containers will accelerate iterative development tasks.  As teams incorporate provisioning and automation practices into the application platform, interest in NoOps and DevOps has grown.

The DevOps movement creates a collaborative environment bridging development and operation team members. DevOps enables team members to jointly design, build, and deploy business application and service solutions. The environment closes the gap between business requirements, policies, available run-time resources, and solution development. PaaS offerings often support DevOp practices, which include self-service, automated provisioning, continuous integration, and continuous delivery. As Dan Juengst describes in his ‘What is Platform as a Service’ blog posting, “At a high-level, a PaaS helps organizations, specifically developers, realize the benefits of cloud computing by providing a fast and scalable way to host applications in the cloud.”

While NoOps provides a needed focus on reducing iteration time and removing provisioning impediments, the current NoOps and mainstream vendor PaaS story has significant limitations:

  1. Minimal in-band automated governance
  2. Does not address how a PaaS improves run-time application behavior
  3. Fails to evolve platform abstraction

Make DevOps and NoOps a cornerstone of improving your software delivery; just don’t think NoOps PaaS entirely defines ‘What is True, Complete PaaS’.   A comprehensive PaaS evaluation framework will help you develop an adoption roadmap.

What PaaS goals do you have beyond increasing your DevOps or NoOps competency and accelerating environment delivery?

Published at DZone with permission of Chris Haddad, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)


Fahmeed Nawaz replied on Tue, 2012/06/12 - 11:10am

What if the same thread calls requestStart() (after an uncaught exception say)? Will a new connection be assigned or the existing one used?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.