Cloud Foundry: The Gaps
summary
BNY Mellon runs Cloud Foundry inside a homegrown PaaS (15 years, 13,000 IT staff, $29.1T assets under custody) and finds specific gaps: non-HTTP/TCP routing and Docker pulls from secure registries, rigid OS certification needs, complex buildpack customization, lack of multi‑datacenter failover orchestration, and secrets/SSO constraints. The bank fills them with an external assembly descriptor system for multi‑component apps, a single control plane across data centers, bespoke secret management and vendor integrations, and selective use of Cloud Foundry for 12‑factor and microservice workloads.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 2:41BNY Mellon
- 7:11Audits
- 8:01Separation of Duties
- 8:34Additional Challenges
- 8:52Disaster Recovery
- 9:25Regulatory Compliance
- 10:17Challenges
- 10:40Open Source
- 11:03Cloud Foundry
- 11:51Gaps
- 12:58OS Certifications
- 13:37Cloud Foundry Disaster Recovery
- 14:08Single Control Plane
- 15:42Docker
- 17:18Billpacks
- 18:26TCP Router
- 19:16Assemblies
- 20:06Assembly
- 21:01dependency management
- 22:13affinity
- 23:07shared local file system
- 23:28single signon
- 24:11secrets
- 26:05summary
- 28:57simplified app deployment
- 29:24innovation centers
- 29:55finance and cloud
related talks
30mBanking on Cloud Foundry Platform: A Case Study of Digital Business Banking Applications
48mCloud Foundry - your PaaS on OpenStack
33mCloud Foundry Weekly: Live at CF Day Germany
27mCloud Foundry Compared with Other PaaSes
24mExpand Cloud Foundry for the Enterprise - Tim Leong, Comcast
33mPublic Cloud Foundry Platforms in Europe: What Have We Learned and Where Can We Go Next?
02mCloud Foundry
02mCloud Foundry