.NET Cloud-Native Bootcamp

Brandon Chavis, Solutions Architect at AWS, shares why CoreOS Tectonic works so well with AWS. 12/12/16

The document discusses how Kubo can be used as a gateway to running cloud-native workloads. It outlines different types of workloads like code developed internally which may change frequently or code from third parties. For internally developed code, Kubo allows maintaining existing processes while deploying container images instead of infrastructure. For external code and data-centric workloads, Kubo provides benefits like health management, multi-cloud support, and operating system/Kubernetes upgrades without affecting applications. The document calls developers to run workloads on Cloud Foundry Container Runtime and share experiences.

Cloud native is a new paradigm for developing, deploying, and running applications using containers, microservices, and container orchestration. The Cloud Native Computing Foundation (CNCF) drives adoption of this paradigm through open source projects like Kubernetes, Prometheus, and Envoy. Cloud native applications are packaged as lightweight containers, developed as loosely coupled microservices, and deployed on elastic cloud infrastructure to optimize resource utilization. CNCF seeks to make these innovations accessible to everyone.

This talk will provide an overview of the PaaS (Platform as a Service) landscape, and will describe the Cloud Foundry open source PaaS, with its multi-framework, multi-service, multi-cloud model. Cloud Foundry allows developers to provision apps in Java/Spring, Ruby/Rails, Ruby/Sinatra, Javascript/Node, and leverage services like MySQL, MongoDB, Reddis, Postgres and RabbitMQ. It can be used as a public PaaS on CloudFoundry.com and other service providers (ActiveState, AppFog), to create your own private cloud, or on your laptop using the Micro Cloud Foundry VM. The talk will end with a demo of Cloud Foundry in action, showing the end to end development workflow, from developing locally with Micro Cloud Foundry to deploying on Cloud Foundry.com. If you want to get started with Cloud development, bring your laptops, check the requirements and download pre-requisites at https://cloudfoundry.com/micro, and we'll help you setup your environment and get started with Cloud Foundry on your local machine.

The document discusses continuous integration, continuous deployment, and infrastructure as code for modern applications. It describes how AWS services like CodePipeline, CodeBuild, CodeDeploy, and CloudFormation can be used to automate the build, test, and deployment of serverless and containerized applications. Continuous integration ensures code changes are built and tested regularly. Continuous deployment enables automated deployments to staging and production. Modeling infrastructure as code allows infrastructure changes to be released predictably using the same tools as code changes.

Hackathons are fun events where developers innovate, learn and build development communities. Whether conducted in an academic setting or a corporate one, the aim is to rapidly produce functional code implementations focused around one or more designated themes. Cloud Foundry is a perfect target platform for hackathons, since it supports fast application deployment for continuous integration, abstracted infrastructure, and ample technology choices in terms of buildpacks and services. For those less familiar with cloud computing, Cloud Foundry provides an ideal opportunity for participants to be introduced to new application hosting techniques (Platform as a Service) and learn keys concepts of building applications for the cloud. Cornelia Davis from Pivotal Software and Catherine Spence from Intel share their experiences in leveraging Cloud Foundry in support of numerous hackathons. They discuss what worked well, and less so, and share with you why and how you can deliver your own hackathon event.

What’s in a cloud platform? Turns out, often several clouds! Companies automate operations in a cloud by treating all components as commodities. However, at enterprise- scale, different business requirements dictate deploying multiple clouds including: - Hybrid infrastructures and multiple cloud providers - Compliance with country privacy laws and different security standards - Specialization requests The most advanced Pivotal Cloud Foundry (PCF) customers engineer their entire cloud platform, including their multitude of PCF instances, as a product. They create pervasive automation, treat their infrastructure as code, and continuously test and update their platform with delivery pipelines. In this webinar we’ll discuss how companies are scaling operations of their multi-cloud platforms with Pivotal Cloud Foundry. We’ll cover: - Why enterprises deploy multiple clouds - What operational challenges this causes - How PCF customers are applying DevOps techniques and tools to platform automation - An idealized tool stack for a engineering a multi-cloud platform at scale - How to improve your platform engineering We thank you in advance for joining us. The Pivotal Team Presenter : Greg Chase, James Ma, Caleb Washburn, Pivotal

Using Google Cloud Services with Spring Boot and Pivotal Cloud Foundry (Pivotal Cloud-Native Workshop: Milan)

This document summarizes a presentation about using CloudFoundry and Kubernetes together. It discusses how CloudFoundry BOSH can provide release engineering, deployment, and lifecycle management for Kubernetes clusters through a project called CF Container Runtime (CFCR). This allows using Kubernetes for container orchestration while leveraging BOSH capabilities. It also presents Pivotal's approach to providing a unified platform for developing, deploying and managing applications on CloudFoundry and Kubernetes through shared services, security, networking and other capabilities.

During this presentation, we will be going over the basics of CloudFoundry, the open-source PaaS solution, one of the biggest open-source projects in existence at the moment, and Pivotal's CloudFoundry offering more specifically. Watch the livestream at https://www.youtube.com/watch?v=Voze6PodQEE

The declarative programming model of Kubernetes is markedly different from what most developers are used to. That the API is a set of resources rather than a list of methods on objects is a bit mind bending. But this programming model is not entirely new – rather, it smacks quite heavily of functional programming. Functional programming had mostly been relegated to academic endeavors until recently. What’s changed that is that our apps are now distributed systems and are simply too complex for us to reason about without help. Kubernetes helps. In order to effectively use Kubernetes to deploy and manage your workloads you need to understand some of the principles of functional programming and how they surface in K8s. In this session I will cover these underlying principles of the K8s programming model so that you can up the robustness and manageability of your application deployments. Presented at KubeCon Barcelona, May 2019

This document discusses Unity's approach to building a large scale Kubernetes infrastructure by distributing ownership of shared components across development teams. Key aspects include: 1. Dividing over 200 microservices across 20 development teams, with each team owning deployment of their services through shared build pipelines, Terraform modules, and Helm charts. 2. Using shared infrastructure components like cloud resources, networking, monitoring tools, and databases that are developed and maintained through an "internal open source model" with clear ownership. 3. Standardizing on tools like Terraform, Kubernetes, Helm, Jenkins, and GitLab CI to ensure consistent environments and enable independent deployments by each team.

Red Hat OpenShift Container Platform 4 Overview Different Application Deployment methodologies on OpenShift though Web-console

IBM presentation at the O'Reilly Open Source Convention Container Day in Austin, Texas on May 9, 2017. https://conferences.oreilly.com/oscon/oscon-tx/public/schedule/detail/61403 New technologies seem to arrive fast and furious these days. We were just getting used to our new container world when serverless arrived. But is it better, faster, and cheaper, as the hype suggests? Daniel Krook explores a real application packaged using popular open source container technology and walks you through a migration to an event-oriented serverless paradigm, discussing the trade-offs and pros and cons of each approach to application deployment and examining when serverless benefit applications and when it doesn’t. You’ll learn considerations for using serverless API frameworks and how to reuse some of your containerization strategy as you move from more traditional application models to an event-driven world. Daniel Krook, Software Architect, IBM

This document discusses how NetApp provides solutions to enable DevOps through capabilities like configuration management, CI/CD, containers, cloud/PaaS, and analytics. It highlights NetApp's Ansible modules for automating storage tasks, Trident for dynamic container storage provisioning, and the NetApp Kubernetes Service (NKS) for deploying and managing Kubernetes clusters across clouds. The document emphasizes NetApp's focus on helping customers achieve freedom, speed and efficiency in their DevOps practices through these technologies and an open developer community.

Altoros is a company that helps other companies digitally transform their businesses using technologies like Predix. They offer services like developing new products on Predix, migrating applications to Predix, and providing Predix training. Altoros specializes in event-driven architectures and uses OpenWhisk as an open source serverless computing platform. OpenWhisk allows defining triggers, rules, and actions to build event-driven applications that can be invoked asynchronously and support Docker containers.

This document discusses strategies for modernizing applications to run successfully on cloud platforms like Pivotal Cloud Foundry. It outlines key principles like the Twelve Factor App methodology and establishing clear objectives and metrics. The document also presents a maturity model for applications and an incremental approach to migrating and optimizing existing applications over time. It analyzes which aspects of the Twelve Factors usually require more or less effort during modernization. Finally, it proposes starting the journey by identifying suitable applications and pushing some all the way to production to establish best practices.

This document outlines an agenda for a .NET cloud-native bootcamp. The bootcamp will introduce practices, platforms and tools for building modern .NET applications, including microservices, Cloud Foundry, and cloud-native .NET technologies and patterns. The agenda includes sessions on microservices, Cloud Foundry, hands-on exercises, and a wrap up. Break times are scheduled between sessions.

This document provides an overview of Docker and cloud native training presented by Brian Christner of 56K.Cloud. It includes an agenda for Docker labs, common IT struggles Docker can address, and 56K.Cloud's consulting and training services. It discusses concepts like containers, microservices, DevOps, infrastructure as code, and cloud migration. It also includes sections on Docker architecture, networking, volumes, logging, and monitoring tools. Case studies and examples are provided to demonstrate how Docker delivers speed, agility, and cost savings for application development.

This document summarizes a presentation about deploying PHP applications to Cloud Foundry. The presentation covers Cloud Foundry concepts like buildpacks, services, and scaling applications. It includes demos of pushing a simple PHP app and binding it to a MySQL database service, as well as scaling the app and performing zero downtime deployments. The presentation is aimed at PHP developers and helping them understand how to design their applications to take advantage of Cloud Foundry and the cloud.

At this joint NYC Cloud Foundry and NY PHP meetup, we'll discuss the shift to Platform-as-a-Service and what it means for PHP development on the cloud. First, we'll take a look at the "traditional" cloud Infrastructure-as-a-Service (virtual servers and disks) model and describe how Platform-as-a-Service builds upon it to provide the runtimes and data services for hosting PHP applications. We'll then demonstrate how a PHP developer can use buildpacks and services within a Cloud Foundry PaaS to deploy scalable and resilient apps to his or her cloud of choice. Along the way we'll compare the variety of buildpacks available to PHP developers, show techniques for binding to services, and highlight best practices for creating born-on-the-cloud apps based on a microservices architecture. Special thanks to Dan Mikusa for helping with the buildpack comparison. PHP developers: Please give all three build packs a try. Provide your feedback and submit pull requests on GitHub.

How to build "AutoScale and AutoHeal" systems using DevOps practices by using modern technologies. A complete build pipeline and the process of architecting a nearly unbreakable system were part of the presentation. These slides were presented at 2018 DevOps conference in Singapore. http://claridenglobal.com/conference/devops-sg-2018/

PCF: Platform for a New Era - Kubernetes for the Enterprise - London Cornelia Davis Sr. Director of Technology, Pivotal 28th March 2018

This presentation discusses how IBM UrbanCode Deploy can automate deployment across platforms from mainframe to mobile. It enables continuous delivery by automating deployment processes for traditional and cloud applications. The tool provides visibility into deployments across environments and manages configurations. It supports deployment of applications to various platforms including mobile, middleware, and mainframe systems of record.

This document discusses Red Hat's cloud platforms, including Infrastructure as a Service (OpenStack), Platform as a Service (OpenShift), and container technologies. It notes that business demands are driving IT transformation toward cloud-based architectures using open source technologies. Red Hat is a top contributor to OpenStack and OpenShift and offers integrated products like Red Hat Atomic Enterprise and OpenShift Enterprise to help customers deploy and manage container-based applications at scale across hybrid cloud environments.

Tout comme le Cloud IaaS avant lui, le serverless promet de faciliter le succès de vos projets en accélérant le Time to Market et en fluidifiant les relations entre Devs et Ops. Mais sa mise en œuvre au sein d’une entreprise reste complexe et coûteuse. Après 2 ans à mettre en place des plateformes managées de ce type, nous partagons nos expériences de ce qu’il faut faire pour mettre en œuvre du serverless en entreprise, en évitant les douleurs et en limitant les contraintes au maximum. Tout d’abord l’architecture technique, avec 2 implémentations très différentes : Kubernetes et Helm d’un côté, Clever Cloud on-premise de l’autre. Ensuite, la mise en place et l’utilisation d’OpenFaaS. Comment tester et versionner du Function as a Service. Mais aussi les problématiques de blue/green deployment, de rolling update, d’A/B testing. Comment diagnostiquer rapidement les dépendances et les communications entre services. Enfin, en abordant les sujets chers à la production : * vulnerability management et patch management, * hétérogénéïté du parc, * monitoring et alerting, * gestion des stacks obsolètes, etc.

12-Factor App is a methodology for building web applications, software-as-a-service apps. Software applications that are Easy to Setup, Portable, Cloud Platform Ready, CI/CD Ready and Scalable.

Jelastic PaaS for Hosting companies, Telcos & MSPs. Jelatic allows hosting companies to enter to the DevOps market and monetize trendy Docker technology

Slides from Workshop 'Cloud Foundry: Hands-on Deployment Workshop' http://www.meetup.com/CloudFoundry/events/150601282/ In this workshop you will learn Cloud Foundry fundamental concepts, setup, deployment and operations. We’ll cover a couple of alternatives to deploy CF in a local environment for learning and testing purposes as well as deploying Cloud Foundry atop IaaS production level environment, being able to manage hundreds of components and thousands of applications. If you did not have a chance to work with Cloud Foundry, it may be useful to test its features locally at first. Deploying this environment on a local machine allows you to get hands-on experience in the solution and, in case you are a contributor, to test some features before you commit them to a production environment.

- Docker celebrated its 5th birthday with events worldwide including one in Cluj, Romania. Over 100 user and customer events were held. - The Docker platform now has over 450 commercial customers, 37 billion container downloads, and 15,000 Docker-related jobs on LinkedIn. - The event in Cluj included presentations on Docker and hands-on labs to learn Docker, as well as social activities like taking selfies with a birthday banner.

How to introduce containers in your organization and how to approach and make the team adopt the technology

The document discusses leveraging cloud technologies for agile software development projects. It begins with an introduction that outlines challenges with agile development and how the cloud can help address issues like slow provisioning times and a lack of infrastructure agility. It then provides overviews of Software as a Service (SaaS), Platform as a Service (PaaS), and Infrastructure as a Service (IaaS) models. The remainder includes demonstrations of using cloud services for cross-browser testing, deploying an application to a PaaS, and discusses factors to consider around IaaS vs. PaaS and public vs. private cloud implementations.

This document is a slide presentation by Ronak Banka on using Pivotal Cloud Foundry (PCF) and Google Cloud Platform (GCP) together. It discusses how PCF provides a platform for deploying applications on GCP that enables both developer and operator productivity through features like automated deployments, service integration, and operations. It also highlights benefits of using PCF on GCP like performance, scale, cost savings, and access to differentiated GCP services.

I gave this presentation on IBM's Open Cloud Architecture and Cloud Foundry at the XCITE conference in Tokyo.

This document discusses modernizing apps using Docker and the 12 Factor methodology. It begins by thanking sponsors and introducing new organizers. It then provides an overview of the evolution of application architectures from the late 90s to today. It notes the benefits of using Docker, such as faster deployments, version tracking, and security. It discusses moving from a monolith application to a microservices architecture using Docker and following the principles of the 12 Factor App methodology to address challenges of distributed systems, rapid deployments, and automation. The 12 factors are then each explained in detail and how Docker can help implement them for building modern, scalable apps.

Cloud Foundry is an open source platform as a service (PaaS) that supports deploying, running, and scaling applications. It is multi-language, multi-framework, multi-cloud, and provides services for data, messaging, and more. Cloud Foundry automates infrastructure provisioning and application lifecycle management so developers can focus on code instead of operations. It allows for cloud portability across public and private clouds. BOSH is used behind the scenes to deploy and manage virtual machines and containers in Cloud Foundry.

Avishay Sebban, Partner Senior Solution Architect at Red Hat IGC, gives the comprehensive idea behind Red Hat Ansible platform, the full automation capabilities and the smooth deployment to cloud. From Cloud Migration Through Automation: Next Level Flexibility virtual event, hosted on September 30, 2020

Spring into AI presented by Dan Vega

The document summarizes Matthew Quinn's presentation on "What AI Means For Your Product Strategy And What To Do About It" at Denver Startup Week 2023. The presentation discusses how generative AI could impact product strategies by potentially solving problems companies have ignored or allowing competitors to create new solutions. Quinn advises product teams to evaluate their strategies and roadmaps, ensure they understand user needs, and consider how AI may change the problems being addressed. He provides examples of how AI could influence product development for apps in home organization and solar sales. Quinn concludes by urging attendees not to ignore AI's potential impacts and to have hard conversations about emerging threats and opportunities.

This document discusses the evolution of internal developer platforms and defines what they are. It provides a timeline of how technologies like infrastructure as a service, public clouds, containers and Kubernetes have shaped developer platforms. The key aspects of an internal developer platform are described as providing application-centric abstractions, service level agreements, automated processes from code to production, consolidated monitoring and feedback. The document advocates that internal platforms should make the right choices obvious and easy for developers. It also introduces Backstage as an open source solution for building internal developer portals.

Cardinal Health introduced Tanzu Application Service in 2016 and set up foundations for cloud native applications in AWS and later migrated to GCP in 2018. TAS has provided Cardinal Health with benefits like faster development of applications, zero downtime for critical applications, hosting over 5,000 application instances, quicker patching for security vulnerabilities, and savings through reduced lead times and staffing needs.

Dan Vega discussed upcoming changes and improvements in Spring including Spring Boot 3, which will have support for JDK 17, Jakarta EE 9/10, ahead-of-time compilation, improved observability with Micrometer, and Project Loom's virtual threads. Spring Boot 3.1 additions were also highlighted such as Docker Compose integration and Spring Authorization Server 1.0. Spring Boot 3.2 will focus on embracing virtual threads from Project Loom to improve scalability of web applications.

This document discusses building platforms as products and reducing developer toil. It notes that platform engineering now encompasses PaaS and developer tools. A quote from Mercedes-Benz emphasizes building platforms for developers, not for the company itself. The document contrasts reactive, ticket-driven approaches with automated, self-service platforms and products. It discusses moving from considering platforms as a cost center to experts that drive business results. Finally, it provides questions to identify sources of developer toil, such as issues with workstation setup, running software locally, integration testing, committing changes, and release processes.

This document provides an overview of building cloud-ready applications in .NET. It defines what makes an application cloud-ready, discusses common issues with legacy applications, and recommends design patterns and practices to address these issues, including loose coupling, high cohesion, messaging, service discovery, API gateways, and resiliency policies. It includes code examples and links to additional resources.

Dan Vega discussed new features and capabilities in Spring Boot 3 and beyond, including support for JDK 17, Jakarta EE 9, ahead-of-time compilation, observability with Micrometer, Docker Compose integration, and initial support for Project Loom's virtual threads in Spring Boot 3.2 to improve scalability. He provided an overview of each new feature and explained how they can help Spring applications.

Spring Cloud Gateway is a gateway that provides routing, security, monitoring, and resiliency capabilities for microservices. It acts as an API gateway and sits in front of microservices, routing requests to the appropriate microservice. The gateway uses predicates and filters to route requests and modify requests and responses. It is lightweight and built on reactive principles to enable it to scale to thousands of routes.

Speakers: - Anish Patel, Staff SE, VMware - Jérôme Vigne, Application Innovation Specialist, Microsoft

Speakers: - Asir Selvasingh, Principal Architect, Java on Microsoft Azure - Anish Patel, Staff SE, VMware

This document appears to be from a VMware Tanzu Developer Connect presentation. It discusses Tanzu Application Platform (TAP), which provides a developer experience on Kubernetes across multiple clouds. TAP aims to unlock developer productivity, build rapid paths to production, and coordinate the work of development, security and operations teams. It offers features like pre-configured templates, integrated developer tools, centralized visibility and workload status, role-based access control, automated pipelines and built-in security. The presentation provides examples of how these capabilities improve experiences for developers, operations teams and security teams.

Virtual workshop on TAP fully in French Date: May 25, 2023

The document provides information about a Tanzu Developer Connect Workshop on Tanzu Application Platform. The agenda includes welcome and introductions on Tanzu Application Platform, followed by interactive hands-on workshops on the developer experience and operator experience. It will conclude with a quiz, prizes and giveaways. The document discusses challenges with developing on Kubernetes and how Tanzu Application Platform aims to improve the developer experience with features like pre-configured templates, developer tools integration, rapid iteration and centralized management.