Real World Experiences: Cloud Foundry on Windows
summary
Cloud Foundry runs Windows workloads using Garden Windows and Diego binaries, with production customers running dozens of Windows cells and hundreds of app instances across continents. Operators use BOSH Windows (beta) to deploy immutable cells and follow rotate, repair, repave. Developers migrate .NET apps by packing dependencies (NuGet/bin-deploy), swapping Windows auth for UAA/OAuth, externalizing sessions to Redis or SQL, routing logs to Loggregator (cf logs), avoiding GAC/custom HTTP handlers, and incrementally moving to .NET Core and Steeltoe.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:13Poll
- 2:20Value of Cloud Foundry
- 2:49Cloud Foundry on Windows
- 4:44Bosch
- 6:17State of Cloud Foundry
- 7:58Twelve Factor
- 9:10What Have We Learned
- 10:36Database Creation Authentication
- 12:10Service Brokers
- 14:00Implicit Application Authentication
- 14:44Use OAuth
- 15:21Unknown app dependencies
- 16:12Dependency management
- 16:57Session management
- 17:36Database
- 18:04Logging
- 18:55Logging Frameworks
- 20:44Configuration Bits
- 22:21CrossSell Encryption
- 24:05Spring Cloud
- 25:35Future
- 26:24Dotnet Core
- 28:20Shoutouts
related talks
33mCloud Foundry’s New .NET Capabilities
31mWindows Server Containers for Cloud Foundry - Matthew Horan & Sunjay Bhatia, Pivotal
28mImprovements to the .NET Developer Experience on Cloud Foundry
58mYou Can Run THAT on Cloud Foundry?
21mKeynote: Panel: How Google and Microsoft are Using Cloud Foundry To Embrace Multi-Cloud
32mCloud Foundry on Azure
34mA New Way of Deploying .Net Applications at Nasdaq
37mCloud Foundry Diego Overview