As enterprises are embracing DevOps and realizing its benefits, especially in their well-established software stacks, they are challenged with another question with the increasing prominence of DevOps in the cloud applications supported with automation.
The question can be expressed as “why don’t we fully streamline the DevOps processes even further since it is more or less consist of tasks in a highly structured flow?”
The primary hurdle is the presence of physical hardware that requires maintenance in any case, but moving to the cloud and taking advantage of SaaS (Software as a Service) or PaaS (Platform as a Service) products eliminates this layer of complexity and automated DevOps starts to make more sense.
And this concept actually has a recently coined name of “NoOps”, which is gaining foothold in parallel with the cloud adoption.
What is NoOps?
In the simplest way, NoOps can be considered as integrating and automating (wherever possible) DevOps processes. In this sense, it is perceived as an alternative to DevOps or sometimes even as “DevOps” killer, but, it is more like an extension and further streamlining of the DevOps concept.
The term is first identified by Forrester and they emphasize that
“NoOps means that application developers will never have to speak with an operations professional again.”
Indeed, when NoOps is implemented and used in the right way and in the right conditions, it is as beneficial and productive as the name suggests.
However, it requires the right tools and preferably a full cloud presence and it should not be considered as a silver bullet for DevOps needs.
DevOps vs. NoOps
There are certain fields where you have an established DevOps culture and an “Ops” team, such as maintaining critical backend applications, which may include dealing with locally installed hardware and software.
However, in emerging technologies such as mobility, it is not as easy as to find and maintain internal resources for DevOps or you might not have the operations experience that you have already gained in backend applications for decades.
DevOps in Enterprise Mobility
Due to its nature, mobility has its own DevOps challenges:
- Requiring a binary to be installed on mobile devices
- Device and operating system fragmentation making coding, testing and distribution processes demanding
- Binary distribution regulations to mobile devices
- Strict app signing requirements
- Issues with keeping signing identities safe, secure and accessible
- Complex app signing and submission processes that force the use of specific hardware and software.
- Lengthy and complex store submission and review processes causing issues in maintenance of the apps after production
For this reason, we highlight the fact that mobile app development is only the tip of the iceberg and the lifecycle management of mobile apps (the “Ops” part) is as important as the development itself, if not more.
Switching From DevOps to NoOps in Mobile App Development
Achieving NoOps in mobile app development is more difficult but also more important than many other fields due to the problems outlined in the previous section.
For a true NoOps approach in mobility, it is important to be able to prevent the DevOps chain breaking from development to production, which can be achieved with a fully integrated mobility platform in the cloud.
