That in turn requires integration and testing of the code from the developers or even development groups involved in building the application, even if their code did not change at all! In typical IT groups, integration and testing can take up to two weeks. Any code change, no matter how small, requires a rebuild of the entire executable. This simplifies deployment-there's only one executable to install on a server-but it makes development much more complex. In such applications, all of the code that makes up the application is bundled into one monolithic executable. One of the biggest impediments is the traditional application architecture. One of the biggest requirements of cloud-native applications is speed: rapidly delivering and iterating application functionality. Application design: The new microservices architecture However, successfully addressing them increases the probability of delivering an application that meets the needs of an important business initiative. Failing to address any of them is likely to result in an application that fails to satisfy external users and internal constituencies. Testing: Changing the role and use of quality assurance (QA)Įach of these elements is an important part in bringing a cloud-native application into production. Operational integration: Aggregating log and monitoring information to enable application managementĭevOps: Automation across the application lifecycle
The question is, what are the elements of a cloud-native app? There five critical aspects:Īpplication design: The move to microservicesĪPI exposure: Internal and external access via standardized methods One phrase often used for this new application paradigm is " cloud-native apps." That's not a bad way to characterize applications that typically have more rapid release cycles and highly erratic workloads, and use DevOps as an inter-group process methodology. Of all the challenges facing IT as it moves to its new role, perhaps none is more challenging than developing the applications to support "be the business." Simply stated, the traditional application architectures, operations, and pace of development are completely inadequate in this new world. This poses many challenges to "IT as usual," including development and operations processes, learning the language and behavior of a minimum viable product (MVP), building teams that mix IT and business personnel, and finding the right skills mix. IT is changing from "support the business" to "be the business." The nature of IT is changing, from an inward-directed, process automation focus to an outward-directed, business offering focus.
0 kommentar(er)
