Developing and delivering modern apps
Hey. There welcome, my. Name is Bob Hanley i'm with dell technologies, today. We're. Going to discuss four, factors, for modern app success. Application. Infrastructure, strategies, to the cloud native error. The. Reality of today is that, every organization must have a digital presence we're all investing, in how to use technology to create value and share, that value with our constituents and with. The global economy going. Digital it's critical. That organizations, transform. To meet this growing need even. Before the Cova 19 pandemic, IDC. Estimated, 60% of global GDP will, be digital, by 2022. This. Means that, even for physical goods sixty, percent of the value chain will. Be derived via. Digital, means. Whatever. Business you're in success. Will increasingly be, a result of experiences, and insights derived. From data and the software, that drives the digital experience, for. This reason. Organizations. That will achieve success will. Do so by, means of delivering, digital. Services, powered. By data and brought, to life as modern. Apps running, in a multi cloud world. Forrester. Recently, interviewed CIOs. To find, out what their top priorities, are and not, surprisingly. 78. Percent or most of CIOs agree, that improving. Their portfolio, of applications, is a top priority but, interestingly almost, half of those organizations. Have not made any improvements, in the last year or more in, terms. Of where to start surveyed. CIOs, agree that, in order to start delivering great, customer experiences. Enterprises. Must modernize their application, infrastructure, they. Also discussed, the emerging technology, trends that will help them supercharge. Application, improvements, and not surprisingly, they, said that containers, and cloud native will, have the biggest impact. In, fact according. To IDC by, 2022. 90%. Of all applications we developed, and delivered is in cloud native approaches, what's. Truly amazing, is the, sheer volume of applications that. Are going to be developed with these new approaches, IDC. In their most recent future, scape study says. That over 500 million, new apps will be built using cloud native practices, by, 2024. So. Let's, focus in on cloud native technology, what's. Different, about it and how, is it changing the game for applications. Cloud. Native combines. New processes. For, software development on operations, and new, architectures. For applications. And systems in. Terms. Of processes. Traditional. Application, development follows a process called waterfall, which, is characterized, by distinct, phases from. Requirements, gathering to, deployment and maintenance and, each phase is well-defined. With distinct. Exit criteria and handoffs between them. Traditional. Operational, practices, are typify, by ITIL, change management processes. The. Challenge of waterfall, is that it leads to long development cycles, before handing, an application, to ops, while, IT, ops is tasked with keeping an application. Available and secure so they, prioritize, stability, and resist change which, slows, innovation, for. Example my, first job as a software developer, it was 18, months from when, we started gathering requirements, to, the time when we delivered a working, application operations. And that is typical, as you. Know requirements. Change over time and log, lead time for software, development these, two applications, not keeping pace with the needs of users. Processes. For cloud native, applications, are agile, and DevOps agile. Features, rapid, iteration, with quick releases agile. Involves users for feedback throughout the development process the. Goal is to quickly develop, a Minimum, Viable Product.
Get, Feedback, and add more features the. Motto is fail, fast meaning. It's, better to find out right away if the application, is meeting customer. Needs. DevOps, means, that IT ops teams are involved throughout the development process delivering. And managing the, infrastructure, to speed innovation. In. Terms of architectures. Traditional. Application, and architectures, are monolithic meaning, that, all capabilities. Are packaged together in a single payload. Virtualization. Technologies, often used to improve the utilization and, efficiency. Of the underlying hardware think. Of a monolith, as being like a freight train it has awesome power, and capacity but, it, takes a long time to load and is not easy to reconfigure. Cloud. Native applications, are developed in a micro services, architecture, an. Application, is a collection, of loosely coupled components that, are packaged, as micro services, so, they can be deployed scaled. And updated, independently. Those. Independent, services, are packaged, as containers which are lightweight, and have the minimum overhead, think, of a set of containers as being like a fleet of delivery vehicles, each. Has reduced power and capacity but each one is quick to load easy, to replace and overall. The fleet provides, more flexible, and resilient delivery, services, and, just. As a fleet of delivery vehicles needs a dispatcher, to, coordinate, the delivery of service, in cloud, native architectures. Containers. Need an Orchestrator, and, kubernetes. Serves that role it's. Responsible, for scheduling, and monitoring the fleet of containerized, micro services, to, make sure that, applications. Are reliable, scale. Well and deliver. The expected, level of service. There. Are a couple of factors that are slowing down the ability of organizations to take advantage, of cloud native technologies. In their application, portfolio, first. Let's. Discuss those challenges, and then, talk about how Dell technologies, is helping, our customers address, them. If. Applications, are so important, and cloud native approaches, are so compelling, what, is keeping organizations. From making progress faster. Think. Of the first challenge, as being everything related, to day zero or, what's needed to source and stand up a cloud native stack. When. You take a look at cloud native approaches, in the enabling software, you, see a thriving, and dynamic, market that has tons of opportunity. The. Cloud native community, is embraced open-source and, that. Has enabled very rapid, development, of an ecosystem of tools that, can help with creating applications. Architected. As micro services and deployed, in containers, and managed, by kubernetes. Kubernetes. Is, curated, by the cloud native computing, foundation, there. Are 550 member. Organizations. With, 85,000. Contributors, to the CN CF in, his. Top projects, are. Known. As those which are graduated. Or incra baiting and there's actually, 26 of those, so. The. Organizations, are looking at putting. Together a cloud native stack they usually look, at a commercial implementation, of one of those and it, takes specialized, knowledge to make the choices and integrate them to work together.
The. Next challenge area is everything related to day to operations. Provisioning. Resources, applying patches upgrading. New versions. Scaling. Resources, up and down etc the. Benefits, of rapid innovation are many, kubernetes. Is released every month and that's a minimum of 12 times a year but that's. For, just one component of the stack and that doesn't include emergency, patches, when sea bees are discovered, so keeping. Things fresh may present an even more. Challenging. Environment. Than just. Setting them up. The. Third challenge area concerns, technical, debt and the nature of modern applications, no. Organization, can do this in a vacuum there. Are existing environments, that have to be maintained in existing, applications, that run the business and existing, staff with skills that keep things operational. New. Applications, and technologies, need to add value and not have a negative impact on operation so the, question becomes how. Can organizations optimize. Their existing investments, and infrastructure, and people, while. Simultaneously. Adopting. Cloud native approaches, and, this. All takes place in the, backdrop of IT infrastructure, today and that means a multi, cloud world. Whether, private, cloud public. Cloud or edge, locations. Organizations. Need, the agility to place the right workload, in the right cloud for, the right reasons. Let's. Look at a way to address each of these challenges, first. Consider. The challenges with sourcing, and standing up the cloud native stack, when. It comes to assembling, a cloud native platform, don't. Reinvent the wheel. The. Cloud native computing, foundation, is curating, a rich ecosystem. And kubernetes, is only, one of the required pieces for a full cloud native stack it's. Got a run on something, so. Whether your target environment is, a public, cloud or an, HDI, cluster, in a server room you. Need to pick the hardware, infrastructure, and speaking. Of infrastructure, the, virtualization, abstraction. Layer that's. Created by the ayahs is, a crucial, building block as well as, for. Storage and he created data has, to be stored in a persistence, layer. Networking. Is huge in the. World of containers, connections, are constantly, being created and torn down so choosing. A software-defined networking, overlay, and integrating. That into the solution, is crucial, this. All has to fit into the context, of existing system so monitoring, and analytics, are table, stakes for enterprise IT. Kubernetes. Has rapidly become the winner in the race to define a standard orchestration. Layer for, container. To play micro services, and every. Service must, be discoverable, and verified as secure so, an image registry, is a required, part of any cloud native stack. While. The open source community has been a blessing, in terms of providing rapid, evolution, and maturing of these components. The, opposing, curse is that you have to choose to download the upstream bits or, choose among competing commercial, distributions. Having. The expertise, to make intelligent decisions, about, which option to choose for each component is a challenge, unto, itself. With. That done the task then becomes integrating, them so that they all work together in a stable system. Building. A cloud native stack from scratch is complex, and the. Resulting, system is what I like to call a science, project, it's, not a production-ready, platform. Chat. Sakic, likes. To call them Rube. Goldberg, machines. And I, love that image because it communicates, the unneeded complexity. And brittleness, of those, from scratch implementations. The. Bottom line is that, the result of building a platform from scratch is usually a snowflake, one-off, design, it's. Guaranteed, to take a long time to produce and it's unlikely, to be the right environment, with, which to entrust your business critical applications. Contrast. That with our. Approach with Dell technologies, cloud platform, we. Deliver Dell technologies, cloud is a complete, package, we've selected the. Best components. It's. Turnkey, we've. Integrated them so, that they work together out of the box and it's automated, so we remove many of the manual tasks, required, to stand up a cloud native environment, the. Standard, we've, incorporated the latest upstream, source kubernetes, so, you're not locking, in to proprietary, extensions, and it.
Works With today's apps as well and it's. Trusted, it's, running today in production, at some of the leading organizations, who have adopted cloud, native software and techniques. But. Once you get up and running you, need to stay that way. Now. That you've stood up a turnkey platform, congratulations. Because you've reached a zero but standing. Up your cloud platform, happens once then, you, have to keep it fresh. Automation. Is the, key to address the challenges associated with ongoing, operation, of your modern apps infrastructure. For. A production ready platform, you, need to maintain and scale the right service, levels for your modern applications. The. Benefits, of rapid, innovation are, many kubernetes. Is released every month and that's a minimum of 12 times a year but, that's just for one component, of the stack and that doesn't include emergency. Patches, for example those, that are released when CVEs are identified. Automated. Lifecycle, management is a crucial, capability, for keeping things secure reliable. And compliant, the. Whole stack should be updated together. Each component, should be upgraded in the predetermined, sequence to, optimize, the process and eliminate, the potential of failure due, to incompatible. Versioning or changes and best practices, don't, do, this manually. When. It comes to adding capacity, and taking advantage of specific, hardware enhancements it's. Important, to have the option, to employ, a non-disruptive, process. That, allows new notes to, be added to a cluster without, causing, downtime, or negatively, impacting, workload performance. Pre-engineered. Integration, with specific, workload provisioning, and configuration. Capabilities. Can, greatly contribute to an agile. Lob. Initiative. This. Streamlines, infrastructure. Provisioning, across multiple, clusters according. To the needs of the workload a couple. Of specific examples here are automated. Provisioning of a horizon, workload, domain for standing up VDI. Or. Automated. Provisioning of kubernetes. Clusters, as needed. For cloud native applications. With. The right platform, data. Migrations, and other disruptive, events, due to the introduction of new generations, of technology are a thing. Of the past. Automation. Is crucial, for efficient, and secure, operations. It's. Address the challenges, associated with ongoing, operation, of your modern apps infrastructure, but how, does that work with your current infrastructure, and how. Do you acquire these skills that, are needed to support these new capabilities. Your. Existing, investments, are actually. A crucial, asset in, this initiative. Every. CIO that I talked to is focused, on managing, and evolving their application, portfolio, how. Can an organization keep, the lights on and support existing, operations, while. Investing, in new applications and capabilities, to meet lob, objectives. Technical. Debt is sometimes, used to refer to this challenge and I don't like that term because it, implies that existing, applications, or a liability when, in fact they, hold value, that must be optimized, a. True. Modern. Applications, approach leverages. The capabilities, of a diverse, set of services, exposed, through api's. That. Includes existing, data sources and run, the business transactional. Systems as well. As new, algorithms. Analytics. Customer. Experience improvements, mobile. Apps etc, some. Of those may, be implemented through existing monolithic, applications, and some may, be implemented, in new containerized. Micro-services. The. Infrastructure, to support applications. Is evolving, as well many. Organizations. Are well experienced, with virtualization, and are implementing infrastructures, to services, the next step in efficiency, in managing. Their traditional, workloads, as, additional. Service models are being deployed. Organizations. Add things, like containers, as a service, and higher. Level abstractions, for the developers, such as platform, as a service the. Challenge comes when. Fundamentally, different, and incompatible approaches. Are adopted, to these different, service models, problems. Are created if, separate, environments, are adopted, for example one. For traditional workloads, and a separate one for cloud native workloads, if, there. Are different, Hardware in different, supporting teams required, there's, a lot of opportunity, for inefficiencies and, roadblocks, to creating, a successful modern, apps initiative. The pragmatic, approach is to, enhance existing, infrastructure. And staff that, are currently, supporting, virtualized apps and infrastructure. As a service, in a. Way that adds support, for containers. And kubernetes, orchestration. Modern. Applications, will combine, services from both traditional, monolithic apps, and emerging containerized, apps and that.
Makes. Sense it. Makes sense that the same hardware in the same people supporting, them. Hardware's. Expensive, and it, makes sense to get the most from the infrastructure, by. Enabling pools, of resources across both, traditional, and cloud, native workloads, in cloud. Native skills or at a premium, staff. With knowledge of legacy, systems are valuable in their own right you. Can ensure that you maximize the value derived, from both by. Equipping your staff with. Tools that extend their knowledge this, will allow them to support cloud native applications. With, their existing, skill set and you. Can start now by. Adding cloud native capabilities. Incrementally. Choose. An approach that allows you to run both virtualized. Monolithic, applications, as well. As containerized. Microservices, applications, on the same infrastructure. Extend. Your existing people. Skills by. Leveraging familiar, tools that. Can add standard, cloud native capabilities to. Your existing, infrastructure. As a service, a. Pragmatic. Approach to, modern apps leverages. Existing investments. By adding cloud native capabilities, incrementally. Most. Organizations. Are using multiple cloud solutions, today so. How does your modern apps initiative, embrace. Private, and public cloud. The. Key is to, drive for consistency, across all, your clouds. The. Reality, of today's IT environment. Is that, cloud is here to stay at. Dell technologies, we believe that cloud is an operating, model not a place that means. The, cloud is about how information technology is, used to achieve organizational. Goals not, where, applications, run a, modern. Application approach. Assumes that you're building for a multi cloud reality. Where, applications, are run should be driven by business technical. Operational. And financial considerations. Not, compatibility. Limitations. The. Right approach allows. The same VMware container to be moved unchanged, so. Developers, and IT can. Create alignment between application. Needs and infrastructure. Options, we. Call this consistent. Infrastructure. And it's a great way to avoid the costs, associated with porting, applications, to run in different clouds a. Consistent. Operational. Framework that spans all environments. Allows. Policies, and processes to be instituted. In a way that limits operational. Silos. This. Can dramatically, improve governance, security, and compliance as well, as enhancing, DevOps, productivity. A, consistent. Cloud operating, model should extend across all environments including. On-premises. Data centers edge locations. And public, cloud to. Eliminate, problems inherent, and using different tools and teams to, manage different clouds. Architect. Your modern, apps environment. To provide consistent, infrastructure. And consistent. Operations, a true, hybrid, cloud. Now. Let's take a look at an example of an organization that's. Using cloud. Native approaches, to, meet their modern application, needs. Liberty. Mutual is, a, good example of a company that, has harnessed the power of cloud. Native approaches. Their. Leadership understands. That software and applications, are crucial, to their future in fact, it's, so important, that they've. Said they want to become a software company, that sells insurance. With. Traditional, software approaches, they, were experiencing, long lead times to deliver new applications. And users. Of the apps were often disappointed, something. Had to change, when. They saw a short window of opportunity, to enter a new market the. Accident, and health insurance market, in Australia, they, knew they had to move fast, they. Decided, to use a new approach the, cloud native approach to, develop, and deliver software that their brokers would use to quote and manage policies. They teamed with Dell technologies, on framing the application, the. Team had talks with end-users, the brokers and in. Four weeks they, were able to deliver a Minimum, Viable Product. And receive customer, feedback then. Developers. Continued, building the product and in iterations. Integrating. It with back-end systems, adding. Underwriting, quoting. And rating, capabilities, and six. Months later rolled. Out a fully functional, solution, for brokers, they. Were able to go from idea, to taking, revenue, in a new market in six, months. And the. Results, speak for themselves in. Terms, of closing business they've. Achieved a, 40, percent strike, rate which, compares, with a 20% for the industry average. Brokers. Were, able to get a quote out in three minutes compared. To about 10 minutes for, their competitors. They. Were able to take revenue, right away with 200 quotes and 60 policies, within one month of operation. By. Using cloud native approaches. Liberty. Mutual was, able to develop and deliver software quickly, that truly made a difference for their business. Organizations. Today are looking. To modernize, their applications, approach so that they can improve the creation, and delivery of value, to their constituents.
Agile. And DevOps processes. Are, being adopted as a way to speed application. Development and deployment efforts. Cloud. Native capabilities, like containers. With kubernetes, orchestration. Are important. Enablers, of modern apps. Dell. Technologies, has, proven, expertise, in helping, our customers implement. A cloud operating, model and the, infrastructure, needed to support a modern applications, approach in. This. Presentation, I've. Summarized, some considerations. That we've learned in those engagements so. Thanks for listening to this discussion of the, four factors for modern app success. Application. Infrastructure, strategies, for, the cloud native era, my. Name is Bob Hanley, you. Can find me Bob a Twitter handle at, Ganley. Bob and you. Can find more information on this topic. Dell technologies. Dot-com /. Cloud. Thanks. For listening and have a great day.