The document discusses the shift towards cloud platforms and microservices architectures to enable continuous delivery. It argues that platforms are needed to manage the increasing complexity of distributed systems and provide services like deployment, scaling, and monitoring. The Cloud Foundry platform is presented as fulfilling this need by automating operations and allowing developers to focus on building applications instead of infrastructure. The vision is for a ubiquitous, flexible, portable, and interoperable cloud computing environment underpinning a large ecosystem of applications.
14. “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
19. Microservices are great, but they require:
rapid provisioning
basic monitoring
rapid application deployment
devops culture
Per Martin Fowler
20.
21. • Use declarative formats for setup automation, to minimize time and
cost for new developers joining the project;
• Have a clean contract with the underlying OS, offering maximum
portability between execution environments;
• Are suitable for deployment on modern cloud platforms, obviating
the need for servers and systems administration;
• Minimize divergence between development and production,
enabling continuous deployment for maximum agility;
• And can scale up without significant changes to tooling,
architecture, or development practices.
23. • Role based access to resources: the right
people should be able to do things and the
wrong people shouldn’t
• Run specified bits on demand: take code, put
it together with all the rest of the things it
needs and and get it running
• Coordinate cross service configurations: in a
service oriented world, services need to be
configured to connect with each other
• Route public requests to running bits: the
next big thing needs access to the internet
• Read and write persistent data: data has to
live somewhere
• Add and remove resources: scaling is a great
problem to have, but still
• Isolate resources and failures without
isolation and decoupling, that is one big
distributed single point of failure
• Measure performance/health: can’t manage
what you don’t measure
• Detect and determine failure: sometimes,
things get real… but how do you know
• Recover failures: someone is going to have
to clean this mess
• Work tomorrow: when everything you’ve
thought to be true has been shown not to
37. The Cloud Native Advantage:
Simple Patterns
Highly Automated
Scaled with Ease
38. A platform is a promise that the products
will function in ways beyond what’s “written
on the box”; that the product is extensible
and has value provided by an
ecosystem bigger than the original
vendor.
Horace Dediu, 2011
http://www.asymco.com/2011/02/25/the-platform-as-a-promise/
39.
40.
41.
42. 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.
43. We’re focusing on certification to guarantee
portability of apps across clouds.
Make it lasting and durable.
Build the ecosystem of opportunity.
44. 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.
45. 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.
