Managing Distributed Cloud Native Applications Made Easy - Nikolay Valchev, SAP
summary
Describes limitations of Cloud Foundry app metadata leading teams to encode IDs, versions and deployment state into app names and custom scripts. Presents a platform extension service that uses a declarative application model to orchestrate cross-app and service dependency management, route mapping, service instance lifecycle and deployment-specific configuration, and demonstrates this with concrete examples.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:02DISTRIBUTED APPLICATIONS IN THE CLOUD
- 2:17EXAMPLE
- 3:42WHAT ARE THE CHALLENGES?
- 7:56THREE THINGS IT IS GOOD FOR
- 10:11SPRING Music MTA
- 11:07MTA DESCRIPTORS
- 12:06MTA DEPLOYMENT DESCRIPTOR
- 16:40MTA EXTENSION DESCRIPTOR
- 18:34BUILDING MTA ARCHIVES
- 19:39CF DEPLOY SERVICE
- 22:21SUPPORTED OPERATIONS
- 26:34KEY TAKEAWAYS
related talks
08mRun Cloud Foundry at Scale
37mWorkshop on Defining a Reference Model for Cloud-Native Application Delivery
30mApp Delivery in Cloud Native: Where are We? What's Next?
39mA Decentralized Reference Architecture for Cloud-native Applications
35mDeployment and Management in the Age of Cloud Integrated Applications
11mLightning Talk - DevOps @ Scale - The Challenge of Cloud Native Architecture
35mHow to Cloud Ops Like a Boss
42mBeyond CF Push - Managing Large Microservice Applications like a BOSH
