Skip to content

containerized-lifecycle-3.1/7.1-index #17958

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 4, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/architecture/containerized-lifecycle/key-takeaways/index.md
Original file line number Diff line number Diff line change
@@ -1,21 +1,21 @@
---
title: Key takeaways
description: Review the key takeaways for the guide.
ms.date: 02/15/2019
ms.date: 04/20/2020
---

# Key takeaways

- Container-based solutions provide important cost-saving benefits because containers solve deployment problems caused by dependency failures in production environments, thereby improving DevOps and production operations significantly.

- Docker is becoming the de facto standard in the container industry and is supported by the most significant vendors in the Linux and Windows ecosystems, including Microsoft. In the future, Docker will be ubiquitous in any datacenter in the cloud or on-premises.
- Docker has become the de facto standard in the container industry and is supported by the most significant vendors in the Linux and Windows ecosystems, including Microsoft. In the future, Docker will be ubiquitous in any datacenter in the cloud or on-premises.

- A Docker container is becoming the standard unit of deployment for any server-based application or service.

- Docker orchestrators like the ones provided in Azure Kubernetes Service (AKS) and Azure Service Fabric are fundamental and indispensable for any microservices-based or multi-container applications that have significant complexity and scalability needs.

- An end-to-end DevOps environment that supports Continuous Integration/Continuous Deployment and connects to the production Docker environments can provide agility and ultimately improve the time to market of your applications.
- An end-to-end DevOps environment that supports Continuous Integration/Continuous Deployment (CI/CD) and connects to the production Docker environments can provide agility and ultimately improve the time to market of your applications.

- Azure DevOps Services greatly simplifies your DevOps environment by deploying to Docker environments from your CI/CD pipelines. This statement applies to simple Docker environments as well as to advanced microservice and container orchestrators based on Azure.

>[!div class="step-by-step"]
>[Previous](../run-manage-monitor-docker-environments/monitor-containerized-application-services.md)
> [!div class="step-by-step"][previous](../run-manage-monitor-docker-environments/monitor-containerized-application-services.md)