Pivotal Podcasts

In this episode, Andrew and Coté talk about one of his works in progress, a short essay on the operational needs of a cloud platform.

The list so far is:

1. role based access to resources- the right people should be able to do things and the wrong people shouldn’t

2. run specified bits on demand - take code, put it together with all the rest of the things it needs and get it running

3. coordinate cross service configurations - in a service oriented world, services need to be configured to connect with each other

4. route public requests to running bits the next big thing needs access to the Internet

5. read and write persistent data - data has to live somewhere

6. add and remove resources - scaling is a great problem to have, but still

7. record internal and external events - keep track of what changed, when and by who

8. isolate resources and failures - without isolation and decoupling, that is one big distributed single point of failure

9. measure performance/health - can’t manage what you don’t measure

10. detect and determine failure - sometimes, things get real… but how do you know

11. recover failures someone is going to have to clean this mess

12. work tomorrow - when everything you’ve thought to be true has been shown not to be

Visit http://pivotal.io/podcasts for show notes and other episodes.

Subscribe to the feed: http://pivotalsoftwarepodcast.libsyn.com/rss

Feedback: podcast@pivotal.io

• Is shift key avoidance syndrome a condition, or a statement?

• You are going to need a platform, the unfinished manifesto.

• Werner Vogels in 2006: “You build it, you run it.”

• Joe Armstrong’s presentation, Systems that Never Stop

• The 12 Factor App establishes a contract

• Preventative maintenance in Wool.