{"id":4058,"date":"2017-12-07T07:30:58","date_gmt":"2017-12-07T15:30:58","guid":{"rendered":"http:\/\/www.bryanfriedman.com\/?p=4058"},"modified":"2018-10-02T23:23:19","modified_gmt":"2018-10-03T06:23:19","slug":"my-first-springone-platform","status":"publish","type":"post","link":"https:\/\/archive.bryanfriedman.me\/cloudingup\/2017\/12\/07\/my-first-springone-platform\/","title":{"rendered":"My First SpringOne Platform"},"content":{"rendered":"

After two full days at my very first SpringOne Platform<\/a>, my head is spinning. At times I’ve felt excited, lucky, proud, impressed, and overwhelmed — sometimes all at the same time. So what’s the best thing to do when I’m feeling all the feelings? Write about it!<\/p>\n

I’ve been having lots of thoughts that I can’t shake in two key areas so I want to share about them.<\/p>\n

PCF 2.0: It’s a Cloud!<\/h3>\n

During the keynote on Tuesday, among a slew of announcements, Onsi Fakhouri unveiled PCF 2.0. I’m not going to get into the details here, but you can (and should!) read all about it<\/a> and watch Onsi’s incredible presentation<\/a>\u00a0if you haven’t already.<\/p>\n

A few months ago, I caught a glimpse of what was coming with PCF 2.0. When I saw a rough sketch of the “four pillars” on a whiteboard, I thought “Hey! That’s a cloud!” It sounds silly to me now. Of course it’s a cloud! It’s right there in the name. Pivotal Cloud<\/em> Foundry. And PCF 2.0 is its natural evolution.<\/p>\n

\"\"<\/p>\n

To be clear, I’m not interested in having a “what is the cloud?” discussion. (I already get that with my family when they ask me what it is that I do.) Still, it’s fair to say that the cloud encompasses many things these days. Public clouds now offer such a breadth of products and services that it’s hard for some customers to keep up. At the same time, customers have more and more types of workloads and want more and more choices.<\/p>\n

All the public clouds have an app service, a container service, and a functions (serverless) service. Some have more than one of each! They all also offer many data persistence and messaging services. So the concept of Pivotal Cloud Foundry offering these same products makes total sense. PCF is staying just opinionated enough. Like Richard Seroter commented in his summary of Day 1<\/a>, customers will have choices, but not too many. The reality is that customers are running in on-premise data centers. They need workloads to run in hybrid or multi-cloud environments. IaaS isn’t enough to constitute a “private cloud” anymore. But PCF 2.0 sure is. (And it’s not even limited to that<\/em>. It runs on public clouds too, remember!)<\/p>\n

Everyone at SpringOne Platform seems pretty pumped about the announcements. But I’ve heard of other folks wondering why Pivotal introduced PKS when they already have PAS. Some may wonder why anyone would still use PAS once they have PKS. And of course, there are many who don’t yet understand what role serverless has to play and why PFS is even a thing. It’s simple. They are all choices. Did anyone ask Amazon why they didn’t kill their app service once they launched a container service? As Onsi said in his talk, the conversation is not an “OR” conversation. It’s an “AND” conversation. PCF will be able to handle all customer workloads.<\/p>\n

\"\"<\/p>\n

During Wednesday morning’s keynote, I felt a little like a kid eating ice cream for the first time. It was riveting watching Kim Bannerman and Meaghan Kjelland do a PKS demo<\/a> and seeing Mark Fisher show off riff<\/a>. There is such an exciting future for PCF and I’m stoked I get to go along for the ride.<\/p>\n

\n

Introducing PCF 2.0! Exciting day of @pivotal<\/a> announcements. #springone<\/a> pic.twitter.com\/Ado2YQcZY7<\/a><\/p>\n

— Bryan Friedman (@bryanfriedman) December 5, 2017<\/a><\/p><\/blockquote>\n