Главная -> Горничная
No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher. The views, opinions and information видео прно изнасиваловании in this book, including URL and other Internet website references, may change without notice. Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is видео прно изнасиваловании or should be inferred.
Microsoft and the trademarks listed at http: Enterprises are increasingly realizing cost savings, solving deployment problems, and improving DevOps and production operations by using containers. Microsoft has been releasing container innovations for Windows and Linux by creating products like Azure Container Service and Azure Service Fabric, and видео прно изнасиваловании partnering with industry leaders like Docker, Mesosphere, and Kubernetes.
These products deliver container solutions that help companies build and deploy applications at cloud speed and scale, whatever their choice of platform or tools.
Docker is becoming the de facto standard in the container industry, supported by the most significant vendors in the Windows and Linux ecosystems.
Microsoft is one of the main cloud vendors supporting Видео прно изнасиваловании. In the future, Docker will probably be ubiquitous in any datacenter in the cloud or on-premises. In addition, the microservices architecture is emerging as an important approach for distributed mission-critical applications. In a microservice-based architecture, the application is built on a collection of services that can be developed, tested, deployed, and versioned independently.
This guide is an introduction to developing microservices-based applications and managing them видео прно изнасиваловании containers.
It discusses architectural design and implementation approaches using. NET Core and Docker containers. To make it easier to get started with containers and microservices, the guide focuses on a reference containerized and microservice-based application that you видео прно изнасиваловании explore.
This guide provides foundational development and architectural guidance primarily at a development environment level with a focus on two technologies: Our intention is that you read this guide when thinking about your application design without focusing on the infrastructure cloud or on-premises of your production environment.
You will make decisions about your infrastructure later, when you видео прно изнасиваловании your production-ready applications.
Therefore, this guide is intended to be infrastructure agnostic and more видео прно изнасиваловании. After you have studied this guide, your next step would be to learn about production-ready microservices on Microsoft Azure.
The current guide also does not provide видео прно изнасиваловании details on Azure infrastructure, such as information on specific orchestrators. We wrote this guide for developers and solution architects who are new to Docker-based application development and to microservices-based architecture.
This guide видео прно изнасиваловании for you if you want to learn how to architect, design, and implement proof-of-concept applications with Microsoft development technologies with special видео прно изнасиваловании on. NET Core and with Docker containers. You will also find this guide useful if you are a technical decision maker, such as an enterprise architect, who wants an architecture and technology overview before you decide on what approach to select for new and modern distributed applications.
The first part of this guide introduces Docker containers, discusses how to choose between. NET Core and the. NET Framework as a development framework, and provides an overview of microservices.
This content is for architects and technical decision makers who want an overview but who do not need to focus on code implementation details. The second part of the guide starts with the Development process for Docker based applications section.
It focuses on development and microservice patterns for implementing applications using. NET Core and Docker. Видео прно изнасиваловании section will be of most interest to developers and architects who want to focus on code and on patterns and implementation details.
The eShopOnContainers application is a reference app for. NET Core and microservices that is designed to be deployed using Docker containers. The application consists of видео прно изнасиваловании subsystems, including several e-store UI front ends a Web app and a native mobile app.
It also includes the back-end microservices and containers for видео прно изнасиваловании required server-side operations. This microservice and container-based application source code is open source and available at the eShopOnContainers GitHub repo.
We wrote this guide to help you understand the architecture of containerized applications and microservices in. The guide and related reference application will be evolving, so we welcome your feedback! If you have comments about how this guide can be improved, please send them to:. Our new feedback system видео прно изнасиваловании built on GitHub Issues. Read about this change in our blog post.
Mac and macOS are trademarks of Apple Inc. The Docker whale logo is a registered trademark of Docker, Inc. All other marks and logos are property of their видео прно изнасиваловании owners.
Cesar de la TorreSr. NET product team, Microsoft Corp. Bill WagnerSr. Mike Pope Steve Hoag Participants and reviewers: About this guide This guide видео прно изнасиваловании an introduction to developing microservices-based applications and managing them using containers.
How to use this guide The first part of this guide introduces Docker containers, discusses how to choose between. Related microservice and container-based reference application: Send us your feedback! Видео прно изнасиваловании you have comments about how this guide can be improved, please send them to: Product feedback Sign in to give documentation feedback Content feedback You may also leave feedback directly on GitHub.
There are no open issues.