August 2021 Summaries

DevOps is a cultural practice that combines development and operations into a single team to deliver high-quality applications quickly, with a focus on breaking down silos and shared responsibilities across the application lifecycle. Azure Pipelines, a Continuous Integration/Continuous Delivery (CI/CD) system, facilitates automated application deployment and maintenance by building, testing, and deploying code efficiently. It supports various tools, languages, and deployment targets, enabling continuous testing and automating build-deploy-test workflows. The Pulumi task extension for Azure DevOps integrates infrastructure deployment with application builds in the same pipeline, requiring a service connection to an Azure Subscription and use of the Pulumi CLI. Developers may not always configure pipelines themselves, but understanding the build and deployment process is crucial, and the Pulumi task extension is compatible with various CI/CD systems beyond Azure.

Pulumi has introduced a range of new features and updates across its ecosystem, enhancing support for cloud providers, Pulumi CLI, and core technologies. The EKS Pulumi Package now includes additional options for managed node groups following improvements from AWS, while the Azure Native provider has added new resources related to networking and IoT security. Pulumi has also updated its methods for Component Packages, allowing components' methods to be available in all languages, and improved the functionality of the dependsOn option to consistently wait on component dependencies, supporting more complex workflows like Kubernetes and Helm. Moreover, Pulumi now permits the use of aliases with providers, facilitating easier stack and code refactoring without disrupting resources. Additionally, Pulumi Service links Azure Native resources directly to the Azure Portal, providing streamlined access for management.

In an exploration of deploying applications on Azure Kubernetes Service (AKS), various methods are discussed, including the use of Helm, manifests, and infrastructure as code. The article begins by setting up an AKS sandbox with a container registry, followed by steps to create and manage container images. It offers detailed instructions on deploying an NGINX container using Helm, as well as deploying a custom container by building an image with Docker and using Kubernetes manifests. The deployment process involves creating a resource group, registering a custom container, and using kubectl to manage deployments and services, emphasizing the importance of integrating cloud engineering practices for versioned and repeatable infrastructure management. The piece concludes by hinting at further exploration into DevOps practices with Azure in subsequent discussions.

In the context of evolving cloud architecture, microservices gained prominence in 2011, and Docker's introduction in 2013 revolutionized application development by simplifying containerization. This shift led to the rise of container orchestration platforms, with Kubernetes emerging as the leading solution due to robust community and corporate backing, widely supported by major cloud providers like Azure. Kubernetes enhances application scalability and accessibility by streamlining container deployment and management. This document provides a detailed guide on configuring and deploying Kubernetes on Azure, specifically through Azure Kubernetes Service (AKS), which offers a hosted Kubernetes solution where Azure manages the master nodes and users manage the worker nodes. AKS supports various features such as autoscaling, integrated logging, and monitoring, as well as networking options, improving the developer experience with integrations like Helm and Visual Studio Code. The guide illustrates the step-by-step process of deploying an AKS cluster using both the Azure Portal and infrastructure as code, emphasizing the advantages of code-based deployment for complex or production environments, with further resources available on GitHub for different programming languages.

Static web applications are gaining popularity due to their speed, security, and cost-effectiveness, and Azure offers two main options for deploying them: Azure Blob Storage and Azure Static Web Apps. The former involves serving static content like HTML, CSS, and JavaScript directly from Azure Storage containers, which can be managed via the Azure Portal or automated through code using languages like C#, Python, or TypeScript. Azure Static Web Apps, on the other hand, integrates with GitHub or Azure DevOps to automate the build and deployment process using frameworks such as React, Angular, and Vue, with hosting enhanced by a Content Delivery Network. This method also allows for serverless API endpoints via Azure Functions and supports a full DevOps workflow using tools like Visual Studio Code and Pulumi. The article emphasizes the flexibility of infrastructure as code, enabling developers to use their preferred tools and environments while maintaining robust deployment pipelines.

The article explores the concept of serverless architecture, specifically focusing on Azure Functions, which are event-driven and execute code in response to triggers such as webhooks or HTTP requests. Serverless provides benefits like automatic scaling, cost efficiency, and reduced maintenance for applications with variable demand or infrequent usage, but it may not be suitable for applications requiring constant running or quick response times due to potential cold start issues. The article provides a practical guide to creating and deploying serverless functions using Visual Studio Code and the Azure Functions extension, detailing the process from setting up a local environment to publishing on Azure. It highlights the advantages of using infrastructure as code for deploying Azure Functions, emphasizing the repeatability and customization it offers, despite seeming more complex than using the Visual Studio Code extension or Azure CLI. The text concludes by encouraging readers to experiment with creating Azure Functions in different languages to understand the process better, and it teases a future exploration of Azure static websites.

Aspiring Azure developers and infrastructure specialists can begin by understanding the fundamentals of virtual machines (VMs), which are pivotal for migrating applications from dedicated hardware, providing full control over software installation, storage, and networking configuration. Azure offers various methods for creating and configuring VMs, including the Azure Portal and Azure CLI, with the process involving selecting an operating system, configuring storage and CPU-memory ratios, and setting up administrator accounts and inbound ports. While creating a single VM can be straightforward using the Azure Portal, managing complex applications with multiple VMs for components like web servers and databases is more efficiently handled through infrastructure as code and cloud engineering methodologies, such as Pulumi's Azure Native provider. This approach allows automation of the build, deployment, and management processes, making them repeatable and reducing errors, thereby providing a scalable solution for provisioning and maintaining cloud infrastructure.

Pulumi's Cloud Engineering Platform is designed to help organizations adopt cloud engineering best practices by applying software engineering principles to infrastructure management, application development, and security. The platform is increasingly popular across diverse industries and engineering disciplines, as evidenced by the growing number of job postings requiring Pulumi skills. Case studies from Atlassian, SANS Institute, and Skai demonstrate how teams leverage the platform to enhance productivity, reduce maintenance time, streamline deployment processes, and achieve greater agility and innovation. Atlassian's Bitbucket team improved developer productivity and reduced maintenance time by using Python for infrastructure as code, while SANS Institute achieved a 70% reduction in deployment times by replacing inflexible legacy tools with Pulumi. Skai successfully migrated its core monolith service from a data center to AWS, utilizing Python and creating modular infrastructure components for improved collaboration. These examples highlight the platform's ability to simplify complex cloud infrastructure tasks and enable teams to use familiar programming languages and tools to drive business outcomes.

Azure, a comprehensive cloud platform, offers over 200 products and services for developing, testing, deploying, and managing applications in an integrated environment. This series of articles focuses on five essential cloud tasks for Azure developers: configuring and deploying virtual machines, developing and deploying serverless Azure Functions, deploying static websites, managing containerized applications using Azure Kubernetes Service (AKS), and automating infrastructure deployment with Azure DevOps. Azure Virtual Machines provide Infrastructure as a Service (IaaS) for applications requiring complete control, while Azure Functions offer a serverless model that scales automatically, focusing on business logic without infrastructure management. Static websites are efficiently deployed using Azure App Service and Azure Static Web Apps, benefiting from reduced latency through content delivery networks. AKS supports various use cases, from containerizing existing applications to deploying microservices and machine learning models, with flexibility in deployment methods. Azure DevOps integrates with CI/CD pipelines to automate the building and deployment process, enabling rapid application updates and resource scaling in response to customer demands.