White Papers

Enterprise Container Platform Buyer’s Guide

Issue link: https://read.uberflip.com/i/1344952

Contents of this Issue

Navigation

Page 4 of 10

© 2020 Mirantis Inc. All Rights Reserved. Information is subject to change. | www.mirantis.com Enterprise Container Platform Buyer's Guide 5 to improve productivity across your entire DevOps organization. Complicating matters somewhat, security has become more complex and high-stakes and organizations are faced with the challenge of empowering developers to be productive while protecting themselves against risk. The new application architectures are highly dynamic and scalable, outgrowing traditional security models so the container platform needs to be built f rom the ground up with security in mind. Build with velocity and versatility Velocity is crucial for modern application development� A container platform should remove all unnecessary barriers to developer productivity. There should not be a steep learning curve for developers to build containerized applications� Containerized applications usually start with the developers who are building applications in a local environment - typically their own desktop or laptop. As your container platform grows and you want to onboard new application teams, you do not want to be boxed in due to limitations on the development tools or languages and f rameworks supported� Container platforms need to provide developers a simple and secure way to build containerized applications, either f rom existing code or f rom scratch. They should easily integrate with existing software development tools, including their preferred IDEs (e.g. Visual Studio, Eclipse, IntelliJ), and they should work across different languages and f rameworks (e.g. .NET, Java, Node.JS). Developers should be f ree to adopt any software development patterns while developing on a container platform. Container platforms should also enable the "shift- left" paradigm in software testing and security. Container platforms should enable developers to use a quick and simple way to test their applications locally before checking their work into the downstream software delivery pipeline� Vulnerabilities in the underlying dependencies should be surfaced early in delivery pipeline so that these can be addressed before allowing the application to run in production� This reduces application design defects that "leak" into staging or production environments� Share with confidence and security Today's digital economy requires the ability to innovate rapidly on top of previous innovation and close collaboration among teams. In mid- sized to large organizations, this increasingly involves DevOps teams who embrace Continuous Integration and Continuous Delivery (CI/CD) principles for agile delivery. A container platform should include tools that make it both simple and secure to collaborate on applications while assisting in the rapid delivery of applications through the software pipeline� The platform needs to secure the entire software supply chain, with security gates built into the pipeline. Software that is ready to be pushed out to production needs to be scanned for vulnerabilities, verified and signed by key stakeholders. A trusted registry 1 needs to be provided to store secure software images. Run with flexibility and uniformity Container platforms should be independent of both the underlying inf rastructure as well as the applications and f rameworks, providing a consistent and uniform operating model for different application types intended for different operating environments to prevent lock-in. Once ready to be deployed, containerized applications will run in clusters on-premises or in hybrid and multi-cloud environments. These 1 Consider Docker Trusted Registry (DTR) or Docker Hub.

Articles in this issue

Links on this page

view archives of White Papers - Enterprise Container Platform Buyer’s Guide