And then provided a list of best practices that do work, e.g., Colin strongly recommended against “wasting time on” building new PaaSes from scratch and \u201chiding away\u201d applications for two years \u201cwhile you fall down a Grantt chart.\u201d<\/p>\n
\n“While you are building your application on Cloud Foundry, your competition is wasting their time building their infrastructure.” \u2014Colin Humphreys, CloudCredo<\/em><\/p>\n<\/blockquote>\nBelow are some more of the best practices from this talk:<\/p>\n
\n- \n
starting with someone else\u2019s CF<\/p>\n<\/li>\n
- \n
starting with a small product in a lab environment<\/p>\n<\/li>\n
- \n
creating learning teams<\/p>\n<\/li>\n
- \n
learning from your customers<\/p>\n<\/li>\n<\/ul>\n
![\"cloud-foundry-summit-in-berlin-2015-keynote-cloudcredo-1\"](\"https:\/\/www.altoros.com\/blog\/wp-content\/uploads\/2015\/11\/cloud-foundry-summit-in-berlin-2015-keynote-cloudcredo-11.jpg\")
<\/center><\/p>\n<\/p>\n“Cloud Foundry is not exciting. What you can do with it is.” \u2014Colin Humphreys, CloudCredo<\/em><\/p>\n<\/blockqoute><\/p>\n
![\"cloud-foundry-summit-berlin-2015-keynote-changing-the-enterprise-cloudcredo-2\"](\"https:\/\/www.altoros.com\/blog\/wp-content\/uploads\/2015\/11\/cloud-foundry-summit-berlin-2015-keynote-changing-the-enterprise-cloudcredo-21.jpg\")
<\/p>\n“Cloud Foundry will not differentiate you. You applications will.” \u2014Colin Humphreys, CloudCredo<\/em><\/p>\n<\/center>
\n <\/p>\n
<\/span>Welcome to the Cloud-native Enterprise<\/span><\/h3>\nThe presentation by James Watters and Joshua McKenty from Pivotal continued the discussion of cloud-native technologies in the enterprise with more advice and a success story of Mercedes Benz adopting CF for their intelligent cars.<\/p>\n
![\"cloud-foundry-summit-berlin-2015-pivotal-keynote-james-watters-joshua-mckenty-1\"](\"https:\/\/www.altoros.com\/blog\/wp-content\/uploads\/2015\/11\/cloud-foundry-summit-berlin-2015-pivotal-keynote-james-watters-joshua-mckenty-11.jpg\")
<\/center><\/p>\nThey pointed out that legacy apps are something that makes money today, but does not allow for iterating as fast as desired (according to Casey West, Pivotal). So, the best way to get started with a PaaS without “bringing your baggage” is to begin \u201cgreenfield and work your way back\u201d to porting legacy apps.<\/p>\n
![\"cloud-foundry-summit-berlin-2015-keynote-cloud-native-enterprise-pivotal-1\"](\"https:\/\/www.altoros.com\/blog\/wp-content\/uploads\/2015\/11\/cloud-foundry-summit-berlin-2015-keynote-cloud-native-enterprise-pivotal-11.jpg\")
<\/p>\n“From monolith to 12-factor-monolith Cloud Foundry” \u2014James Watters and Joshua McKenty, Pivotal<\/em><\/p>\n<\/center><\/p>\n
Another major theme of this talk was the importance of enabling metrics and feedback and moving from ticket-driven enterprise cultures to metric-driven ones. James also made a prediction that a common enterprise metric in the next five years will be the percentage of cloud-native software they use, not the degree of virtualization.<\/p>\n
![\"cloud-foundry-summit-berlin-2015-keynote-welcome-to-the-cloud-native-enterprise-1\"](\"https:\/\/www.altoros.com\/blog\/wp-content\/uploads\/2015\/11\/cloud-foundry-summit-berlin-2015-keynote-welcome-to-the-cloud-native-enterprise-11.jpg\")
<\/center><\/p>\n\n“Let’s not wait for Gartner to invent the Cloud Foundry maturity model.” \u2014James Watters and Joshua McKenty, Pivotal<\/em><\/p>\n<\/blockquote>\nJames and Joshua also said some words about the importance of getting feedback in the shortest possible time, so you can build the features that matter, and developing a profound software culture within your organization.<\/p>\n
\n“Gonna have to reinvent your own culture, cause you have your own problems.” \u2014James Watters and Joshua McKenty, Pivotal<\/em><\/p>\n<\/blockquote>\n <\/p>\n
<\/span>Can You Trust Cloud Foundry to Save a Life? To Save 10,000?<\/span><\/h3>\nThe story by Armakuni was about how a team of 5\u20136 people used Bluemix to build a platform that helps the Comic Relief charity to collect donations, 90% of which come during a seven-hour window, once a year.<\/p>\n
![\"cloud-foundry-summit-berlin-2015-keynote-tim-savage-armakuni\"](\"https:\/\/www.altoros.com\/blog\/wp-content\/uploads\/2015\/11\/cloud-foundry-summit-berlin-2015-keynote-tim-savage-armakuni-1024x768.jpg\")
<\/p>\n“A lot of things can go wrong and we can still handle 400 donations\/second.” \u2014Tim Savage, Armakuni<\/em><\/p>\n<\/center><\/p>\n
Armakuni\u2019s platform uses CF and a Concourse CI pipeline to resiliently scale from 0 to 400 transactions per second, despite any failures. It can then scale down to allow for 70% savings during the rest of the year, when the traffic is flat. Using this solution, Comic Relief was able to raise \u00a31,000,000,000 for their activities. The platform\u2019s CI pipeline allows them to deploy code (blue\/green deployments) at any time, even during peak production traffic.<\/p>\n
![\"cloud-foundry-summit-berlin-2015-keynote-armakuni-1\"](\"https:\/\/www.altoros.com\/blog\/wp-content\/uploads\/2015\/11\/cloud-foundry-summit-berlin-2015-keynote-armakuni-11.jpg\")
<\/center><\/p>\n\n“Code deployment has become a non-event.” \u2014Tim Savage, Armakuni<\/em><\/p>\n<\/blockquote>\nTim Savage also listed some of the reasons why Armakuni chose Cloud Foundry, which included horizontal scalability, easy pipelines, resourcing, portability, and being truly agile.<\/p>\n
<\/p>\n
<\/span>SAP and Cloud Foundry\u2014Love at Second Sight<\/span><\/h3>\nDid you know that, initially, SAP discarded Cloud Foundry as a PaaS option for their platform, but then changed their mind and achieved great results? This was one of several talks on SAP HANA delivered during the summit, focusing on why SAP chose CF and what they have done\/are doing to make the platform more ready for enterprise use.<\/p>\n
Matthias Steiner<\/strong> and Bernd Krannich<\/strong> presented the results of a SWOT analysis of SAP\u2019s CF-based PaaS project done in the third quarter of 2013. Among the three things that they loved most about CF are its being the de-facto standard PaaS, support for multiple deployment models, and openness.<\/p>\nSAP had to make some difficult decisions and overcome a number of serious challenges when moving to the cloud. E.g., they decided to stick with CF, which was all about Linux until recently, although SAP is mainly a Windows shop. They had to introduce a number of changes into their internal procedures and software-defined networks. Finally, they had to ensure the right degree of security to satisfy the requirements of their enterprise customers, namely:<\/p>\n
\n- \n
stemcell\/stack hardening<\/p>\n<\/li>\n
- \n
separating admin and developer access<\/p>\n<\/li>\n
- \n
two-factor authentication<\/p>\n<\/li>\n
- \n
encrypted everything<\/p>\n<\/li>\n
- \n
traceability\/auditability\/certification<\/p>\n<\/li>\n
- \n
controlling BOSH deployments, etc.<\/p>\n<\/li>\n<\/ul>\n
The talk also featured the list of SAP\u2019s contributions to the CF ecosystem and some other interesting statistics, which you can find in this slide deck.<\/p>\n