Home Architecture Introducing ‘Enterprise Cloud Native’

Introducing ‘Enterprise Cloud Native’


‘Cloud Native’ is the definition that has emerged to capture the software design approach intended entirely for Cloud deployment, characterized by the integrated use of containers, microservices architecture and continuous deployment models.

Enterprise Cloud Native

The scope of activity is defined by the software development lifecycle only – Enterprise Cloud Native expands this scope to consider the full landscape of other technologies and deployment challenges a typical large enterprise organization will face, including but not limited to:

Legacy / Hybrid Cloud

Working only with pure Cloud-based services is an ideal most enterprises are a long way from reaching yet; the production environments they must work with and deploy to will also feature a variety of legacy platforms and technologies. CIO.com explores this question.

Innovative Digital Solutions

The fundamental purpose of Cloud Native, to speed the process of releasing new digital innovations, highlights the nature of this challenge. For example retailers might want to roll out cryptocurrency payments to their Point of Sale terminals.

The challenge of doing so was noted in this Scotsman article, highlighting that many enterprises will find their legacy IT environments aren’t yet capable of easily integrating new technologies like Blockchain.

IT Service Management

New, accelerated approaches to software development and deployment will have considerable impact downstream on the IT Service Operations team, captured in this AWS blog by Mark Schwartz previously CIO of a major US Government agency, where he notes:

“In my role as CIO of USCIS I once made the mistake of not paying enough attention to that portion of ops that lies outside of DevOps. We had a large initiative going on with about 15 agile teams. When they released code into production, they found that they needed to set up a process for handling user problems and questions, production incidents, and monitoring alerts. As the system became more complex, this burden became heavier. In a few cases, business leaders as well as teams working on other systems downstream and upstream complained that they hadn’t been notified of outages that affected them.”

In our blog review of Nirmata we highlight how new vendors are addressing this challenge, synthesizing ITIL procedures with DevOps practices, with other vendors such as Stackarmor identifying the same market need and positioning their technologies to address “The DevOps Gap“:

The Cloud Best Practices Network is a global practitioner community for Digital Transformation and Cloud Computing.


Your email address will not be published. Required fields are marked *