Download to read offline
Uploaded byMike Melusky
Container Orchestration for .NET Developers
The document presents a talk by Michael Melusky on container orchestration for .NET developers, focusing on Microsoft Azure and Amazon AWS as cloud providers. Key topics include the benefits of serverless computing, the differences between .NET Framework and .NET Core, and practical demonstrations of deploying .NET Core applications using Azure Functions and AWS Lambdas. Finally, it highlights containerization strategies with Docker and Kubernetes for managing applications in a cloud environment.
Softwareā¦
More Related Content
Similar to Container Orchestration for .NET Developers
Container Orchestration for .NET Developers
- 1. Container Orchestration for .NETDevelopers Mike Melusky ā Philly.NET
- 2. About me ā¢ MichaelMelusky (@mrjavascript) ā¢ Lives in Harrisburg, PA ā¢ Software Developer for Audacious Inquiry in Baltimore, MD ā¢ College Professor (Penn State / Franklin and Marshall) ā¢ BBQ and Lawn Care ā¢ XBOX One ā¢ Regular speaker at Philly.NET events (Code Camps and Monthlies)
- 3. What are wetalking about tonight? ā¢ āDot Netā ā¢ Amazon AWS and Microsoft Azure ā¢ Serverless Computing ā¢ AWS Lambdas and Azure Functions ā¢ Docker ā¢ Kubernetes ā¢ Container Registries (ACR and ECR) ā¢ Containers as a Service with Amazon ECS and Microsoft AKS
- 4. Amazon v. Microsoft ā¢Iām not here to cheerlead for either Microsoft or Azure ā¢ If you are tasked with the decision of migrating from a hosted region to the cloud ā¢ Please donāt use this talk as sole factor in your decision ļ ā¢ This decision takes significant research ā¢ Weighing pros and cons
- 5. Themes for Tonight ā¢Serverless Architecture ā¢ Being able to deploy a product without having to worry about underlying infrastructure ā¢ Portability ā¢ If you ever need to migrate from Amazon to Microsoft or vice versaā¦ ā¢ How difficult will that be?
- 6.
- 7. Dot Net ā¢ Ispoke here (at Code Camp) back in November ā¢ Showcased containerization of numerous technologies (Java, Python et al.) ā¢ Focusing solely on āDot Netā this evening ā¢ What is Dot Net?
- 8. Dot Net ā¢ SoftwareFramework from Microsoft ā¢ You can use it for building any type of app ā¢ Mobile, Web (MVC), Micro-Service ā¢ Two flavors: ā¢ .NET Framework ā¢ .NET Core ā¢ What is the difference between each?
- 9. .NET Framework ā¢ Frameworkfrom Microsoft ā¢ Runs primarily on Windows systems ā¢ Does not run on Linux ā¢ Latest version is 4.8 (April 2019) ā¢ Does not support C# 8.0
- 10. .NET Core ā¢ Frameworkfrom Microsoft ā¢ Cross-platform (can run on Windows, Linux and Mac OSX) ā¢ Current version is 3.1 ā¢ C# 8.0 is supported!
- 11. .NET Standard ā¢ .NET Standardis a set of APIs that all .NET platforms must implement
- 12. Why .NET Core? ā¢We are focusing on .NET Core tonight ā¢ Main advantage: cross-platform! ā¢ Letās look at a .NET Core MVC app ā¢ ** DEMO **
- 13.
- 14. Traditional āWeb Deployā ā¢ Traditionallywe can deploy a .NET Core application to IIS server ā¢ Right click on project and ādeployā ā¢ How else can we deploy? ā¢ Where can we deploy to?
- 15.
- 16. Cloud Providers ā¢ Tonightweāre going to look at two cloud providers ā¢ Amazon and Microsoft ā¢ Amazon AWS ā¢ Microsoft Azure
- 17. Amazon AWS ā¢ On-demandcloud computing platform ā¢ Servers in 22 geographic regions ā¢ 60+ managed services ā¢ Managed services such as services for queueing, relational database services, caching ā¢ Two managed services we are interested in for tonight: ā¢ AWS Lambdas ā¢ Containerization Services
- 18. Microsoft Azure ā¢ Cloudcomputing platform ā¢ Servers available in 52 geographic regions ā¢ Multiple managed services very similar to AWS ā¢ Such as Cosmos DB, Azure Cache, Azure Search, et al ā¢ Of note for tonight: ā¢ Azure Functions ā¢ Azure Container Services
- 19.
- 20. Functions ā¢ Relate aninput to an output ā¢ Examples: ā¢ X^2 (squaring) ā¢ X^3 + 1 ā¢ Trigonometric functions (sin, cos, tan)
- 21. How does thisrelate to Azure and AWS? ā¢ Both cloud providers offers āfunctionsā ā¢ Allows you to run a āquick piece of codeā on Microsoft/Amazonās hardware ā¢ Azure Functions: runtime cannot exceed 5 minutes ā¢ AWS Lambdas: runtime cannot exceed 15 minutes ā¢ Letās look at both providers
- 22. Example Function ā¢ Letāslook at a sample function ā¢ Calculate area of a circle
- 23. Creating Azure Function ā¢Letās implement the previous example with an Azure Function ā¢ Can write the function in a variety of languages ā¢ Letās use .NET Core ā¢ Install āAzure Developmentā option with Visual Studio ā¢ ** DEMO **
- 24. Creating AWS Lambda ā¢Now letās do the same with AWS! ā¢ Like Azure, many languages are supported (Java, Python, etc.) ā¢ Like before, letās use .NET Core ā¢ The Visual Studio project templates come from AWS Toolkit for Visual Studio: https://aws.amazon.com/visualstudio/ ā¢ ** DEMO **
- 25.
- 26. Whatās the differencebetween the two? ā¢ We implemented the same function for different cloud providers ā¢ Both are .NET Core implementations ā¢ Looking at the code can the AWS Lambda run in Azure Functions? ā¢ And vice versa?
- 27. Functions in CloudProviders ā¢ Functions/Lambdas are provider dependent ā¢ Hypothetically consider the case of an AWS customer ā¢ With 100+ Lambdas ā¢ Requirement to migrate the cloud infrastructure to Azure ā¢ How will the lambdas transfer? ā¢ (Spoiler alert: rewrite)
- 28. āFunctions as aServiceā (FaaS) ā¢ Both AWS Lambdas and Azure Functions fall under the āFunctions as a Serviceā model (FaaS) ā¢ Developers simply write the code and run the application ā¢ Donāt have to worry about the infrastructure management
- 29. Acronyms ā¢ IaaS āInfrastructure as a Service ā¢ Caas ā Containers as a Service ā¢ PaaS ā Platform as a Service ā¢ FaaS ā Functions as a Service
- 30. Serverless Architecture ā¢ Cloudprovider runs the server ā¢ Customer pays for the resources that are consumed
- 31. Benefits of ServerlessComputing ā¢ As a developer (thatās you), donāt need to worry about the following: ā¢ Security updates ā¢ Anti-virus software ā¢ Operating System Updates ā¢ Hardware Upgrades ā¢ You simply write, deploy and run code!
- 32. Serverless Computing ā¢ Sincewe identified that the servers are managed by the cloud provider ā¢ What do we know about the underlying infrastructure? ā¢ Mostly abstracted, but we can assume: ā¢ Linux! ā¢ (Azure has Windows in Preview discussion coming soon)
- 33. Linux ā¢ Since thesehost servers run Linux, the code we write needs to run on this operating system ā¢ Main reason why we want .NET Core! ā¢ .NET Core is cross platform (Windows, Mac OSX, Linux) ā¢ You canāt write AWS Lambdas using .NET Framework 4.8
- 34. TL;DR; version ā¢ Asdevelopers, we like Serverless Computing ā¢ If weāre working with .NET Core deployment is a breeze ā¢ Only downside so far? ā¢ Lambdas and platforms are provider dependent ā¢ Is there a solution where we have serverless benefits but also cloud provider independence?
- 35. Before we getto Dockerā¦
- 36. Azure Service Fabric ā¢Platform as a Service (PaaS) from Microsoft ā¢ Allows you to build and deploy micro-services with ease ā¢ Runs in containers ā¢ Facilitates solutions for communication between micro- services ā¢ Also facilitates container orchestration
- 37. Building a Backend ā¢Choice for building a backend API for front end apps ā¢ Technically you can run your backend API in AWS Lambda ā¢ Not necessarily purpose of Lambda, meant for quick, serverless code invocations ā¢ Can use Azure Service Fabric for the backend ā¢ Main downside of Azure Service Fabric? ā¢ You are locked in with Azure ā¢ Is there a portable alternative?
- 38.
- 39. Docker ā¢ Docker issoftware which provides the concept of application containerization ā¢ Uses OS virtualization under the hood
- 40. Containerization? ā¢ A techniquewhich allows you to deploy distributed applications without launching a virtual machine for each app! ā¢ Each application (or instance of the application) is isolated from each other ā¢ All code and resources and configuration needed to run the application is part of the container ā¢ Containers differ from virtual machines
- 41. Virtual Machines vs.Containers
- 42. Docker ā¢ Can installthe Docker Engine from Docker Hub ā¢ Docker Desktop is available for Mac OSX and Windows ā¢ With Docker for Windows, Windows 10 Professional is required ā¢ Virtualization is needed
- 43.
- 44. Docker Images ā¢ DockerContainers are instances of Docker Images ā¢ So for us to run our applications in the Docker Engine, we will need to build a Docker Image (coming soon) ā¢ For now letās look at the Docker Command Line Interface (CLI) ā¢ As well as some common commands
- 45. ādocker imagesā ā¢ Willshow all ātop levelā images ā¢ Included in response is the tag, the size, creation date
- 46. ādocker psā ā¢ Listsall running containers ā¢ If you want to see all containers (e.g. stopped containers) ā¢ docker ps āa
- 47. Running a DockerImage ā¢ docker run ā¢ Allows you to run container using an image ā¢ docker stop ā¢ Allows you to stop a particular container
- 48.
- 49. Building the .NETCore Image ā¢ To run the .NET Core application in Docker we need to build an image to run on the Docker engine ā¢ For building images, we are required to provide a Dockerfile
- 50. Dockerfile ā¢ A Dockerfileis a file that lists instructions needed for building a image ā¢ Based off a source image ā¢ You can run OS commands in the Dockerfile as well (move, copy, et al.) ā¢ You can also expose any port numbers your application uses
- 51. Dockerfile ports ā¢ Generallyfor web applications we expose either 80 or 8080 ā¢ We can also expose the secure ports if we want as well (443 and 8443) ā¢ Docker allows you to port forward from a source port ā¢ For instance if you want to expose 5050 as your external port and route to the internal (exposed) port 80, Docker allows this ā¢ Incredibly useful for cloud providers where AWS/Azure will assign these ports dynamically at runtime
- 52. Dockerfile and .NETCore ā¢ Letās build our application for Docker ā¢ That is produce an image using a Dockerfile ā¢ And then run the image on the Docker engine ā¢ ** DEMO **
- 53.
- 54. Docker and .NET ā¢With the Docker image we just build, we build for .NET Core ā¢ With this .NET Core image, the image can run on any host operating system (Windows, Linux, et al.) ā¢ What about .NET Framework (4.X)? ā¢ Yes, you can containerize a .NET Framework application! ā¢ However this image can only run on Docker Engine on Microsoft Windows hosts
- 55.
- 56. Containers as aService (CaaS) ā¢ We saw Functions as a Service earlier tonight ā¢ Do cloud providers have the same ability except being able to run Docker containers on demand? ā¢ Yes!
- 57.
- 58. Kubernetes (K8S) ā¢ Open-sourcecontainer orchestration software ā¢ Will monitor the health of the containers ā¢ If a container dies, Kubernetes will restart the container
- 59. Kubernetes ā¢ Used inmany applications ā¢ For instance, Red Hatās OpenShift platform is based on Kubernetes ā¢ The Telcom industry uses it for cable management and routing! ā¢ Both Microsoft and Amazon offer managed services for Kubernetes clusters ā¢ Amazon offers EKS (Elastic Kubernetes Service) ā¢ Azure offers AKS (Azure Kubernetes Service)
- 60. Waitā¦ ā¢ The Meetup.comdescription for this event ā¢ Listed āNo Kubernetes Required!ā ā¢ Unfortunately, we will be using some K8 tonight ā¢ At least with Azure
- 61. Containers as aService (CaaS)
- 62. Containers as aService (CaaS) ā¢ Both Amazon and Microsoft offer the managed service for running your containers ā¢ Both Microsoft and Amazon offer two different managed services for each ā¢ One managed service is based on proprietary technology ā¢ The other managed service is based on K8 ā¢ Letās look in the console for each ā¢ ** DEMO **
- 63. Containers and CloudProviders Provider Managed Service Service Type Notes Amazon Elastic Container Service (ECS) Proprietary Elastic Kubernetes Service (EKS) Kubernetes Microsoft Azure Container Service (ACS) Proprietary End of life 1/31/2020 Azure Kubernetes Service (AKS) Kubernetes
- 64. About Me ā¢ Ipersonally use AWS for both full time job and side projects ā¢ ECS is used actively in each ā¢ When preparing this session, I emailed a Microsoft Developer ā¢ I was able to contact someone on the Azure Product Team ā¢ Azure team member was confused about this presentation, and told me to learn Kubernetes ā¢ Microsoft is sunsetting (end of month) Azure Container Services (ACS) and is mandating customers migrate to Azure Kubernetes Services (AKS)
- 65. Amazon and ECS ā¢What I also found out from this exchange ā¢ Amazon considers ECS a legacy product ā¢ Eventually customers will presumably need to migrate to EKS ā¢ If Microsoftās decision is any predictor of future events
- 66. Plan for Remainderof Tonight
- 67. Plan for Tonight ā¢Originally was planning to show both ECS and ACS ā¢ Technically I can still demonstrate ACS since itās available for one more week ā¢ But there would be more value doing the same demonstration using AKS
- 68. Amazon AWS -ECS ā¢ Proprietary solution from Amazon to dynamically run and orchestrate Docker containers ā¢ You can specify how many instances of the application you want to run ā¢ ECS will automatically scale up and down the instances based on load ā¢ Make sure your code can run in parallel and be careful about mutual exclusion and locking!
- 69. Amazon AWS ECS ā¢For running Docker images in the cloud ā¢ Amazon needs to be able to pull your image from a repository ā¢ You have a few options ā¢ If your image is public, you can simply push to Docker Hub ā¢ However most code is proprietary, and the general public shouldnāt be allowed to pull the image
- 70.
- 71. Amazon ECR ā¢ ElasticContainer Registry ā¢ Managed service from Amazon to store Docker images (as well as their tags) ā¢ Microsoft offers a similar managed service ā¢ Azure Container Registry (ACR)
- 72. Pushing to containerregistry ā¢ To push to ECR ā¢ (1) Build the image (using docker build) ā¢ (2) Obtain credentials from Amazon (with docker login command) ā¢ (3) Optionally tag the image (otherwise latest is default tag) ā¢ (4) Push the Image to ECR (or ACR) using docker push ā¢ ** DEMO **
- 73.
- 74. Amazon ECS tasks ā¢With ECS, each instance of the Docker image is based off an ECS Task ā¢ An ECS task specifies: ā¢ Which Docker image is used ā¢ How much memory each instance ā¢ How much vCPU should be allocated ā¢ Letās create our ECS task for the .NET Core application ā¢ ** DEMO **
- 75.
- 76. Running the taskin ECS ā¢ With our ECS task created, now we can create the service in ECS ā¢ When we do this, we need to specify the Docker Engine the task will run against ā¢ Amazon gives you two options ā¢ Docker Engine on an EC2 instance you provide (virtual machine) ā¢ AWS Fargate (serverless!)
- 77. AWS Fargate ā¢ Serverlessapproach for running Docker images ā¢ Containers run on Amazonās underlying Docker Engine ā¢ Under the hood: LINUX ā¢ With regards to .NET, .NET Core will work with Fargate since itās cross platform ā¢ .NET Framework 4.8 WILL NOT WORK with Fargate since that requires Windows Docker Engine ā¢ You can use ECS with .NET Framework but a backing Windows EC2 instance is needed!
- 78. AWS Fargate ā¢ Letāscreate a service now in ECS for our task ā¢ And run our .NET Core application in AWS Fargate ā¢ ** DEMO **
- 79. Letās Do theSame With Azure!
- 80. Similarities to AWS ā¢As mentioned earlier, Microsoft is ending Azure Container Services (ACS) ā¢ We need to spin up a Kubernetes cluster in AKS ā¢ There are some similar steps however ā¢ Letās push our Docker image to Azure Container Registry (ACR) ā¢ Letās then deploy our image into AKS (using their serverless runtime called Azure Container Instances or ACI) ā¢ ** DEMO **
- 81.
- 82. Serverless Matrix Provider ManagedService Type Host OS Notes Amazon AWS Lambda FaaS Linux ECS/EKS Fargate CaaS Linux Fargate support for EKS added 12/2019 Microsoft Azure Functions FaaS Linux AKS with Container Instances CaaS Linux and Windows Windows is in Preview
- 83. Next Steps forMe ā¢ Since I use AWS ā¢ Spin up EKS cluster for personal micro-services ā¢ Test and eventually cut over from ECS ā¢ But will bite the bullet and learn Kubernetes
- 84. Learning K8 onAzure ā¢ Kubernetes Learning Path 2.0: ā¢ https://azure.microsoft.com/en-us/resources/kubernetes-learning- path/
- 85. Thank you forcoming
- 86. Thank you forComing ā¢ Visual Studio Solution (code) is on Github ā¢ https://github.com/mrjavascript/phillynet_jan2020 ā¢ Slides on SlideShare ā¢ @mrjavascript