CEO Sam Ramji LinuxCon keynote on the end of competitive advantage and the increase in foundations across the software ecosystem.

1. @sramji
Sam Ramji, CEO
Cloud Foundry Foundation
The Making of a Cloud Native Platform

2. The Dawn of a New Era

3. Internet All The Things

4. A shift in human behavior

5. A shift in business matching
the shift in human behavior

6. Since 2000, 52% of the Fortune
500 are no longer on the list

8. Continuous Innovation

9. January 21: Cloud Foundry Foundation
June 21: Node.js Foundation
June 22: Open Container Initiative

10. Question 1:
Why are there so many foundations?

11. Open source has won. Popular projects
are now economically attractive.
This breeds competition and distrust.

12. The move to foundations to drive multi-
vendor open source enables
competing corporations to collaborate.

15. + =

16. http://cloudfoundry.org

17. Opening the development roadmap
Standardizing through certification

19. vs.

20. + =

21. http://nodejs.org
Foundation

22. Governing the development roadmap
Setting release dates and quality standards

24. vs.

25. OCI+ =

26. http://www.opencontainers.org
Open Container Initiative

27. Standardizing the file format
Standardizing the runtime

28. dockerfile + appc → filesystem
libcontainer → runC

29. Food for thought

30. As of 2010, the 9 largest projects were governed by non-profit foundations.
The 10th largest was an order of magnitude smaller.
“There appears to be a glass ceiling limiting the growth
of the large single-vendor projects.”
Henrik Ingo, 2010
http://openlife.cc/blogs/2010/november/how-grow-your-open-source-project-10x-and-revenues-5x
Linux
KDE
Apache Eclipse
Perl
Mozilla
Gnome DrupalGNU

31. Question 2:
How do all these technologies work together?

32. Any meaningful technology
has a movement around it

33. For Linux,
the movement was
open source

34. We now live in an age of
open source

36. We live in an age of
open source datacenters

37. Carrier Networking
Datacenter Networking
Datacenter Operating Systems
Hardware
Virtual Machines
Operating Systems
Application Platforms
Programming Frameworks
Containers

38. Any meaningful technology
has a movement around it

39. For Cloud Foundry,
the movement is
continuous innovation

40. Continuous Innovation
Continuous Deployment
Continuous Integration

41. Continuous Innovation
Continuous Deployment
Continuous Integration

42. waterscrumfall

43. dev+ops

44. Microservices
Containers
12-Factor Applications

45. Ephemeral
Scalable
Agile

46. Run in the cloud
Support any client device
Connect to legacy data and processes via APIs

47. Right-sizing digital innovation
Focused on cycle time optimization
Smaller teams and faster tools

48. Two-pizza teams
Silo-breaking

49. “Any organization that designs a
system (defined broadly) will produce
a design whose structure is a copy of
the organization's communication
structure.
Melvyn Conway, 1967

50. “When looking to split a large application into parts, often
management focuses on the technology layer, leading to UI teams,
server-side logic teams, and database teams.
When teams are separated along these lines, even simple changes
can lead to a cross-team project taking time and budgetary
approval.
A smart team will optimise around this and plump for the lesser of
two evils - just force the logic into whichever application they have
access to. Logic everywhere in other words.
This is an example of Conway's Law in action.”
James Lewis and Martin Fowler, “Microservices”

51. Users need stability in their cloud
infrastructure to be able to do
continuous innovation.
The developers building the
infrastructure for the cloud need a
way to evolve it rapidly.

52. Borg
Mesos
Cloud
Foundry
Omega
Kubernetes
cgroups
Docker
OCI
rkt/appc
LXC

53. Prescriptive Assembly
CHRONOS
runC
scheduler.next
container.next

54. Prescriptive Assembly
CHRONOS
runC
scheduler.next
gorouter
CloudController Auth
Loggregator
Staging
Buildpacks
BOSH
Service Broker
Diego
Linux
Windows
Docker
etcd
Core
Services
container.next

55. Prescriptive Assembly
CHRONOS
runC
scheduler.next
gorouter
CloudController Auth
Loggregator
Staging
Buildpacks
BOSH
Service Broker
Diego
etcd
Core
Services
container.next

56. Question 3:
What is happening with Cloud Foundry?

57. Cloud Foundry enables continuous deployment of
cloud native apps at scale.
Cloud Foundry runs in multiple clouds.

58. Currently shipping Cloud Foundry

62. We’re rebalancing the system towards user-driven
roadmaps and control of the upstream project.
We’re building support for specific industry
clusters in Financial Services, Industrial IoT, and
Telecommunications.

63. We’re learning a ton about moving a project from
single-vendor open source to multi-vendor open
source.
Explicit controls
Implicit controls
Transparency
Communication

64. We’re focusing on certification to guarantee
portability of apps across clouds.
Make it lasting and durable.
Build the ecosystem of opportunity.

65. We see a world of cloud computing that is
UBIQUITOUS and FLEXIBLE
supporting public, private, and hybrid application environments.
PORTABLE and INTEROPERABLE
enabling users to move their applications wherever they need to go.
VIBRANT and GROWING
underlying a massive ecosystem of applications and developers
based on an efficient marketplace.

66. We see a human community that is
PRAGMATIC
and focused on exchanging practical experience.
DIVERSE
and inclusive of people across race, gender, orientation, and lifestyle.
RESPECTFUL
and committed to listening to thoughtful and honest perspectives.

67. Thank you
@sramji
sramji@cloudfoundry.org

68. Further reading:
The End of Competitive Advantage (McGrath)
http://12factor.net (Wiggins)
Migrating to Cloud-Native Application Architectures (Stine)
Microservices (Fowler)
https://github.com/opencontainers/specs
https://github.com/opencontainers/runc + http://runc.io
http://cncf.io
http://cloudfoundry.org