Skip to main content

CF Summit 2018


I just returned from CF Summit 2018 in Boston. It was a great event this year that was even more exciting for Pivotal employees because of our IPO during the event. I had every intention of writing a technology focused post, but after having some time to reflect on the week I decided to take a different route.

After all the sessions were complete and I was reflecting on the large numbers of end-users that I had seen present, I decided to go through the schedule and pick out the names of companies that are leveraging Cloud Foundry in some way and were so passionate about it that they spoke about it at this event.   I might have missed a couple when compiling this list, so if you know of one not on here, it was not intentional.

  • Allstate
  • Humana
  • T-Mobile
  • ZipCar
  • Comcast
  • United States Air Force
  • Scotiabank
  • National Geospatial-Intelligence Agency
  • Royal Bank of Canada
  • Capital One
  • Kaiser Permanente
  • Boeing
  • Expedia
  • Garmin
  • Travelers
  • General Electric
  • Charles Schwab
  • JP Morgan Chase
  • Swisscom
  • HCSC
  • Southwest Airlines
  • Bloomberg
  • Liberty Mutual
  • American Airlines
  • Allianz Deutschland AG














This is an impressive list of companies that had the opportunity to speak at this 2 ½ day event. I believe you could put it up against the list of customer/users speaking at any open-source technology conference and it would rank up at the top. This is a testament to not only the technology, but the incredible work done by the engineers who work on Cloud Foundry every day.

My other takeaway was the consistent focus on developer impact and productivity in the sessions I attended.  Aside from a few nuts and bolts sessions that were targeted at those interested in the infrastructure of a Cloud Foundry implementation, almost all the sessions were aimed squarely at how to leverage technology to make software development frictionless.  From CI/CD to secrets management, it was all there and in a developer-friendly format. That is an impressive thing….it’s extremely tough to get a large contingent of techies together and have them talk about productivity and business outcomes instead of ...say… the guts of the new flux capacitor interface.


I was speaking to an industry analyst and was told the only other conference that focuses on customer outcomes is SpringOne Platform.   SpringOne Platform has lots and lots of training and technology focused sessions, but it also an abundance of customer impact sessions. Want to see what I mean?

Take a look at https://content.pivotal.io/springone-platform-2017 for the videos from last years SpringOne Platform.

The 2018 version is looking even better. Come join us in Washington D.C

You can register at https://2018.event.springoneplatform.io/register and use the code S1P300_Anniversary to get $300 off this week!






Comments

Popular posts from this blog

Isilon HDFS User Access

I recently posted a blog about using my app Mystique to enable you to use HUE (webHDFS) while leveraging Isilon for your HDFS data storage.   I had a few questions about the entire system and decided to also approach this from a different angle.   This angle is more of "Why would you even use WebHDFS and the HUE File Browser when you have Isilon?"   The reality is you really don't need it, because the Isilon platform give you multiple options for working directly with the files that need to be accessed via Hadoop.   Isilon HDFS is implemented as just another API, so the data stored in OneFS can be accessed via NFS, SMB, HTTP, FTP, and HDFS.   This actually open up a lot of possibilities that make the requirements for some of the traditional tools like WebHDFS, and in some cases Flume go away because I can read and write via something like NFS.   For example, one customer is leveraging the NFS functionality to write weblogs directly to the share, then Hadoop can run MapRe…

Is Hadoop Dead or Just Much Less Important?

I recently read a blog discussing the fever to declare Hadoop as dead. While I agreed with the premise of the blog, I didn't agree with some of its conclusions. In summary, the conclusion was that if Hadoop is too complex you are using the wrong interface. I agree at face-value with that conclusion, but in my opinion, the user-interface only addresses a part of the complexity and the management of a Hadoop deployment is still a complex undertaking.

Time to value is important for enterprise customers, so this is why the tooling above Hadoop was such an early pain-point. The core Hadoop vendors wanted to focus on how processes executed and programming paradigms and seemed to ignore the interface to Hadoop. Much of that stems from the desire for Hadoop to be the operating system for Big Data. There was even a push to make it the compute cluster manager for all-things in the Enterprise. This effort, and others like it, tried to expand the footprint of commercial distributions of Hadoo…