SE-Radio Episode 239: Andrew Clay Shafer on Modern Platform-as-a-Service

Topics covered
Popular Clips
Episode Highlights
Platform Features
Cloud Foundry distinguishes itself by shifting the focus from server-centric to application-centric primitives, enhancing the user experience for both developers and operators. Andrew Shafer highlights the platform's commitment to strict XP engineering practices and test-driven development, which are deeply rooted in Pivotal's history of application development 1. This approach ensures a seamless deployment experience, contrasting with other tools like Puppet and Chef, which require more expertise 2.
It's not a question of that scale or not a scale. What cloud foundry is doing is shifting the primitive from being a server centric primitive to an application centric or service centric primitive.
--- Andrew Shafer
The platform's open-source nature and robust foundation support its innovative deployment strategies, making it a preferred choice for enterprises and startups alike.
Historical Development
The historical development of Cloud Foundry is rooted in its origins at VMware, where it began as a project with engineers experienced in Google's infrastructure. Andrew Shafer explains that the transition to Pivotal allowed for greater focus and freedom to innovate, leading to the evolution of Cloud Foundry's architecture 1. This shift was crucial in adapting and evolving the platform to meet modern demands.
Cloud Foundry started as a project at VMware, and the majority of the early engineers on cloud Foundry had all kind of come from behind the veil at Google.
--- Andrew Shafer
The platform's development reflects a blend of technical expertise and strategic organizational changes, setting the stage for its current success.
Governance
Cloud Foundry's governance model emphasizes contribution over traditional meritocracy, fostering a community-driven approach to development. Andrew Shafer describes this model as "governance by contribution," where the more code one writes, the more influence they have 3. This approach encourages active participation and collaboration within the community, ensuring that the platform evolves with the needs of its users.
Governance by contribution basically means that, you know, we, we want everyone to write the code. And the more code you write, the more say you get by virtue of the fact that you're writing the code.
--- Andrew Shafer
The foundation's structure, supported by a trillion-dollar market cap, underscores its commitment to open-source principles and community engagement 1.
Related Episodes


SE-Radio Episode 247: Andrew Phillips on DevOps
Answers 383 questions

SE Radio 618: Andreas Møller on No-Code Platforms
Answers 383 questions

SE-Radio-Episode-259:-John-Purrier-on-OpenStack
Answers 383 questions

Episode 216: Adrian Cockcroft on the Modern Cloud-based Platform
Answers 383 questions

SE-Radio Episode 314: Scott Piper on Cloud Security
Answers 383 questions

Episode 499: Uma Chingunde on Building a PaaS
Answers 383 questions

SE Radio 585: Adam Frank on Continuous Delivery vs Continuous Deployment
Answers 383 questions

SE Radio 631: Abhay Paroha on Cloud Migration for Oil and Gas Operations
Answers 383 questions

SE-Radio Episode 320: Nate Taggart on Serverless Paradigm
Answers 383 questions

SE-Radio Episode 355: Randy Shoup Scaling Technology and Organization
Answers 383 questions

Episode 107: Andrew Watson on the OMG
Answers 383 questions

SE-Radio Episode 344: Pat Helland on Web Scale
Answers 383 questions

SE Radio 616: Ori Saporta on the Role of the Software Architect
Answers 383 questions
SE-Radio Episode 332: John Doran on Fixing a Broken Development Process
Answers 383 questions














