Dockercon 2019 Developing Apps with Containers, Functions and Cloud Services

Editor's Notes

• #20: Building on top of the FaaS programming model, Azure Functions keep all the mentioned features and extend your possibilities with additional capabilities that help to reduce your development time and boost productivity, while using best in class tools.
• #21: Additional information Triggers and bindings – https://docs.microsoft.com/en-us/azure/azure-functions/functions-triggers-bindings Monitoring—https://azure.microsoft.com/en-us/services/application-insights/ Local debugging—https://docs.microsoft.com/en-us/azure/azure-functions/functions-run-local#run-functions-locally CI/CD—https://docs.microsoft.com/en-us/azure/azure-functions/functions-continuous-deployment Run locally—https://docs.microsoft.com/en-us/azure/azure-functions/functions-run-local Proxies—https://docs.microsoft.com/en-us/azure/azure-functions/functions-proxies
• #22: Additional information Languages—https://docs.microsoft.com/en-us/azure/azure-functions/supported-languages Dev options— Azure Functions portal—https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-first-azure-function Visual Studio—https://docs.microsoft.com/en-us/azure/azure-functions/functions-develop-vs Visual Studio Code—https://code.visualstudio.com/docs CLI—https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-first-azure-function-azure-cli Java/Maven—https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-first-java-maven Hosting options—https://azure.microsoft.com/en-us/pricing/details/functions/ Durable Functions—https://docs.microsoft.com/en-us/azure/azure-functions/durable-functions-overview
• #23: Azure Functions spans in about 10 separate projects on GitHub About 60 contributors from the community across hundreds of commits All issues and sprints are triaged and tracked fully in the open, anyone can see exactly what code is running in the cloud and what is being worked on next More info in - https://github.com/Azure/Azure-Functions
• #32: And that’s not all! Sure, Terraform plus AKS is a winning combo, but Team Azure is also involved in lots of super-cool k8s ecosystem open source. Take Helm, for example! Which is now a CNCF incubating project - we donated the IP. At this point I always feel like I need to have a content warning for YAML - if YAML upsets you, there will be so much YAML. And we need to manage all that YAML between all our environments and versions! We use helm in AKS, azure dev spaces, azure pipelines, azure devops - this isn’t a “drink our own champagne” story - these tools support us too!
• #33: Helm manages complexity, has easy updates, allows you to easily version and share, and allows for easy release rollback. So let’s go into more detail on each!
• #34: Draft is simple app development and deployment into any kubernetes cluster. Two simple commands is all it takes for developers to start working on container-based applications. Draft also detects the language your applications are written in and uses packs to generate a Dockerfile and Helm Chart based on that programming language.
• #42: Docker Desktop Enterprise Enterprise management & security, developer productivity, local Kubernetes runtime If / when customers ask, “What’s new in Docker Enterprise 3.0?” … this, Docker Desktop Enterprise (DDE), is the biggest ‘new’ thing. Significant value for customers in having a complete, end-to-end platform, from desktop to production, because it enforces app runtime environment consistency from beginning to end. Significant differentiation: Neither Pivotal nor Red Hat yet have a commercially-supported desktop developer environment. The three major feature categories: Enterprise management & security Enterprise IT requires that they, not the developers, control developer’s desktops so as to try and minimize security risks. Docker Desktop Community does not provide for any control by centralized IT. Docker Desktop Enterprise is delivered in standard formats (PKG, MSI) that can be managed by centralized IT tools to roll-out, install, configure, upgrade, and secure DDE on developer desktops. Developer productivity While each customer typically has a small group of Docker experts, automation tools in DDE are designed to enable the non-Docker experts so that all developers at the customer can be productive and successful with Docker. Specifically, DDE automation tools (see list below), automatically generate all the Docker “scaffolding” developers need to containerize their apps, ie, Dockerfiles, Docker Compose files, CI pipeline configurations, and Docker images. Customer business value: Non-Docker expert developers can stay focused on building their applications while still realizing the benefits of the Docker Enterprise platform. The Docker Enterprise platform’s ability to enable developer productivity while not constraining developers to specific app frameworks (as the PaaS vendors, Pivotal PCF and RH OpenShift, do), a significant differentiator. Local Kubernetes runtime Standard, certified Kubernetes - not a fork (in contrast to Red Hat OpenShift …) Local instance of Kubernetes (and Docker) enables developers to rapidly iterate their “write code - compile code - test app” cycle (aka “inner loop”) DDE enables developers to match their local Kubernetes (and Docker) environment with the UCP production ops environment for Kubernetes (and Docker). Keeping dev and ops environments consistent reduces friction between developers and ops, enabling faster delivery of applications into production. The five text blocks on the side speak to specific elements of the above ... Native local … The foundation of DDE “Automated, template-driven” means the following tools ... Docker Application Designer Docker Application Templates Docker Pipeline Docker Assemble Match desktop and server environments … See “keeping dev and ops environments consistent” point above Centrally manage deployment, upgrades, and configuration … via Windows MSI and Mac PKG packages, popular formats for enterprise desktop management tools Commercial enterprise support … Business Day only Heads-up Some enterprise customers, for security reasons, do not allow their developers to run Docker (or Kubernetes) locally on their desktops (as diagrammed in the DTR slide). In these situations, the “inner loop” of the developers “write code - compile code - test app” happens in a “development cluster” that the developer logs in to, not on their desktop. Don’t panic ;-). The Docker Enterprise platform is still relevant in this case (and would enable a “development cluster”), but the customer’s interest in DDE could be less than those customers who allow their developers to execute “inner loop” locally on their desktops.
• #58: Small function – move gradually Decouple – different team (langue agnostic, version …) Centralize place to control your api security and so on…
• #69: Okay, so the new, exciting shiny! Check out cnab.io if you want to jump right in. CNAB: A spec for packaging distributed apps. CNABs facilitate the bundling, installing and managing of container-native apps — and their coupled services. Cloud Agnostic: A CNAB can be composed to utilize whatever infra or services you require - there’s no vendor lock in. Deliverable Apps CNABs can be used to easily deliver apps across teams, organizations and marketplaces - even shared offline. Signed & Secure A CNAB can be cryptographically signed, attested, and verified to ensure a trustworthy source. [building all this on brigade]
• #70: Duffle is a simple command line tool that interacts with Cloud-Native Application Bundles (CNABs) - helping you package and unpackage distributed apps for deployment on whatever cloud platforms and services you use. - duffle-bag is a GUI, too.
• #71: Okay, so that’s a lot. Porter makes using CNAB easier - it’s a declarative bundle builder. When we deploy to the cloud, most of us aren’t dealing with just a single cloud provider or toolchain. The simplest of applications today need nginx, Let’s Encrypt, persistent file storage, DNS, and somewhere in there is your application. One app is installed with Helm, another with the cloud provider’s cli and it’s all glued together with magic bash scripts. That is a lot to figure out! 😅 Porter is a cloud installer that helps you manage everything together in a single bundle, focusing on what you know best: your application. Mixins: classes with methods for use by other classes (while not relying on inheritance). We can describe actions using mixins.