Docker Tools in Visual Studio and Azure
•Download as PPTX, PDF•
1 like•122 views
Visual Studio 2017 Launch local event in Guatemala City. I did a brief introduction to Docker and showed how easily integrates into VS. I also did two deployments to Azure: one for a single container app to Azure App Service and other one to Azure Container Service for a multi container app using Visual Studio Team Services.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Docker Tools in Visual Studio and Azure
Similar to Docker Tools in Visual Studio and Azure (20)
More from Christian Melendez
More from Christian Melendez (20)
Recently uploaded
Recently uploaded (20)
Docker Tools in Visual Studio and Azure
- 2. About me Senior Cloud Engineer @Autoweb Arquitecture + Cloud + .NET + Docker Twitter: @Christianhxc Blog: cmelendeztech.com
- 3. “
- 10. VMs
- 11. Containers
- 13. Some Docker vocabulary Docker Image The basis of a Docker container. Represents a full application Docker Container The standard unit in which the application service resides and executes Docker Engine Creates, ships and runs Docker containers deployable on a physical or virtual, host locally, in a datacenter or cloud service provider Registry Service (Docker Hub or Docker Trusted Registry) Cloud or server based storage and distribution service for your images
- 15. Build/CI, Integrate, Test 3. 1. Monitor and Diagnose Outer-Loop Push Code Production environments Run, Manage 5. 6. Container Service Service Fabric Batch App Services Coming soon … … Code Run Validate Debug Inner-Loop CD, Deploy 4. Visual Studio Team Services Source Code Control (SCC) 2. Azure Container Registry
- 16. Some Assembly Required Batteries are included
- 17. Demo
- 18. Traditional approach Microservices approach
- 19. Traditional approach Microservices approach Microservices approach
- 20. WEB APP Shopping cart service .NET CORE Catalog service JAVA Inventory service RUBY Shipping service .NET CORE Account service PYTHON
- 21. Azure Container Registry Visual Studio Container based CI/CD with Visual Studio Team Services WEB APP Shopping cart service .NET CORE Catalog service JAVA Inventory service RUBY Shipping service .NET CORE Account service PYTHON
- 22. Photo used under CC http://www.wocintechchat.com/ Debug and Deploy Containers Demo
- 23. Announcing .NET Core microservices reference application Explore our beta release and provide feedback: http://aka.ms/MicroservicesArchitecture
- 24. .NET Core microservices reference app Explore our beta release and provide feedback: http://aka.ms/MicroservicesArchitecture e eSHOP onCONTAINERS
- 25. FUNDAMENTALS CLOUD MOBILE DEVOPS
- 26. THANK YOU!
- 27. The leading automotive search company, worldwide. We connect millions of car shoppers with automotive retailers. We’re looking for talent: Senior Software Engineers Interested send your Resume to: recruitment@autoweb.com
Editor's Notes
- Let’s take a look at what build, ship run means in a little more detail, but before that we need to level set some Docker vocabulary and commands: Image The static component that represents a on-running applicatoin Containers are derived from images images contain EVERYTHING an application needs to run Should always be built via a Dockerfile (which we’ll talk about in a bit_ Container The standard unit in which the application service resides Package app and dependencies together Isolated from other containers One container per app / service Docker Engine The program that creates, ships and runs containers Deployable on any physical or vm host locally, in datacenters or cloud Communicates with Docker Hub Registry The service that store, distributes and manages container images Receives commands from Docker Client via Engine Access control with public, private repos
- Build, Ship, Run – Any App Anywhere – that’s Docker’s slogan But, what does it mean? What it essentially boils down to is that developers can choose whatever language or components they want to build their application – .Net, ASP, Java, Ruby, Redis, etc across both the Linux and Windows ecosystem. They are assured that whatever the code up, will run wherever the Ops team chooses to deploy it – Physical, virtual, or cloud – it makes no difference to Docker. An application written on a developers laptop will run exactly the same on the largest bare metal servers, in the cloud, even on a Raspberry Pi in my den. Move applications seamlessly from dev to test to production.