This week we talk with about how organizations are increasingly looking to improve how they use data and workflows around data to innovate in their business. As with discuss with our guest, Sina Sojoodi, More than the usual ideas about “big data” and “machine learning,” we talk about the practical uses of data workflows like insurance claims handling and retail optimization. In many large, successful organizations the stacks to support all this processing are aging and not providing the agility businesses want. Of course, as you can guess, we have some suggestions for how to fix those problems, and also how to start thinking about data workflows differently. We also cover some recent news, mostly around Google Cloud Next and Pivotal’s recent momentum announcement.
So, long run growth comes from one thing, and one thing only: Productivity. New and better ways of doing things. New and better products, new and better companies. It doesn’t come from 90% of the things that we talk about. So, the Federal Reserve, stimulus programs, even anti-inequality programs–over 10-20 years, it’s about productivity. Our ancestors may have, you know, you might have had a grandparent who dug coal with a pickaxe; and how did you get so much richer? Not by your union getting him higher wages and he still digs coal with a pickaxe at 20 cents an hour, not 10 cents. It’s because one guy left and he uses a bulldozer. Right? Growth comes from productivity. And productivity–everybody likes growth in someone else’s backyard. Productivity comes from new companies, doing things new ways, and making life very uncomfortable for everybody else. Uber is the great example. Uber is–that’s a great productivity enhancement. It’s putting a lot of people to work who otherwise couldn’t go to work. And the taxi companies hate it. And most of economic regulation is designed to stop growth. It’s designed to protect the old ways of doing things. So, what we need for growth-oriented policies is exactly that kind of innovation, that kind of new companies coming in an upending the status quo, that make everybody uncomfortable and run to their politician to say, ‘You’ve got to stop this.’
I don’t know the politics of economics enough to figure out if that’s a dick thing to say or not, but it sure makes grim-sense. The rest of the interview has some fun mental gymnastics and suave “turns out”’ing.
(And check out the show notes! That’s some intimidating work.)
Eventually, you have to decide how your open source software is going to make money, and your partners probably won’t like it. That’s what the dust-up around Docker is this week, it seems to us. We also talk briefly about VMware’s big conference this week, and rumors of HPE selling off it’s Software group to private equity.
Check out the full show notes for links to the recommendations, conferences, and tech news items we didn’t get to cover: https://cote.io/sdt71
I have a discount code for Operability.IO, September 19th and 20th in London. I hear good things about this conference; check out their talks from last year. It has a good list of speakers, including our very own Casey West. You can 10% off registration if you use the code COTEMEMOOIO16.
Nippers – “Nippers learn about safety at the beach. They learn about dangers such as rocks, and animals (e.g. the blue-ringed octopus), and also about surf conditions, such as rip currents, sandbars, and waves. Older Nippers also learn some basic first aid and may also learn CPR when they reach the age of 13.”
Docker Inc. doesn’t want to be a commoditized building block From a Red Hat person: “The conflict started to escalate earlier this summer, when Docker Inc used its controlling position to push Swarm, it’s own clone of Kubernetes-style container orchestration, into the core Docker project, putting the basic container runtime in a conflict with a notable part of its ecosystem. Docker Inc. then went on to essentially accuse Red Hat of forking Docker – at the Red Hat Summit no less. After that, Docker Inc’s Solomon Hykes came out strongly against the efforts to standardize the container runtime in OCI – an initiative his company co-founded.”
A fight over where to draw the line between free/open/commodified and costs/proprietary/competitive: “And while I personally consider the orchestration layer the key to the container paradigm, the right approach here is to keep the orchestration separate from the core container runtime standardization. This avoids conflicts between different layers of the container runtime: we can agree on the common container package format, transport, and execution model without limiting choice between e.g. Kubernetes, Mesos, Swarm.”
Don’t bring a pistol to a bazooka fight. Enterprises love RHEL – have you ever tried to sell Ubuntu into organizations? It’s like what selling NT must have been like.
If you’re in the container orchestration space, do you need to open source your platform? We use Mesosphere’s recent open sourcing of it all to discuss that topic, plus marketing in the container world and an ongoing arm-chair stratagizing of what’s going on the infrastructure software market right now with respect to containers.
Total funding to date: $126m – sweet Jesus! That’s a lot of DevOpsDays and O’Reilly conference booths!
Investors: Andreesen Horowitz, Khosla Ventures and Fuel Capital, with new investors A Capital and Triangle Peak Partners – Microsoft and HPE
From Jay’s longer report, March 2nd, 2016: “Mesosphere does not disclose its number of paying clients, but says it has dozens of large enterprise customers, its primary target. The company says its experience supporting software deployments in production is among its key differentiators, helped by the use of Apache Mesos by companies such as Twitter, Netflix, Airbnb, PayPal and Yelp, which was featured in a 451 User Deployment Report. Mesosphere says its focus is customer deployments of 500-1,000 nodes per day in production. It also says the bulk of its customers are licensees with professional services accounting for less than 10% of its clients, which tend to move to its subscription software.”
Q for Brandon: do you need to be open source to succeed in infrastructure? What’s your reflection across BMC, Sun, Zenoss, CA, Boundary, Solarwinds, and now IBM? You’ve dealt in all the things, in various stages of maturity: what’s the play you need here?
Previously reported NPS scores were an error, actually trending up
Mistral no longer last most popular project (re; StackStorm Brocade acquisition)
A listener from Devoxx Poland contacted Coté about speaking there. THE DRUGS ARE WORKING!
Getting into Google Play Podcast – first of all: “Google, welcome to the party. (Oh, and fuck you – again – about Google Reader. I’m still bitter).” Second, I had to resubmit my verification email because I use cote.io at WordPress now, and they don’t do catch-all email because stupid reasons I could give a shit about, I’m sure – I went into Feedburner and redid it, and now am awaiting Google to send an email to itself so I can go enter the claim code into Google. WHAT A TIME TO BE ALIVE.
Matt: Shaquille O’Neal voice for Waze: My kids love this, they don’t even know who he is. Also: Hitler uses Docker. Funnier than I expected, “Even enterprises want to run Docker now and they still have Red Hat 5 installed.” Classic Programmer Paintings.
We’re media sponsors of DevOpsDays Seattle, Minneapolis, and Chicago. In upcoming episodes we’ll have a discount code, and we’ll be giving away one ticket to each. Email us up at firstname.lastname@example.org and tell us why we should give you the ticket.
In this podcast with Michael Coté, who works at Pivotal in technical marketing, he and The New Stack founder Alex Williams talk about current production systems and development environments for building applications. According to Coté, Pivotal describes these new systems and environments as “cloud native.”
Over the course of this interview, Coté discusses best practices and illustrates three requirements for cloud native development and deployment: utilizing the patterns of microservices architecture, implementing a DevOps approach, and striving for continuous delivery as the primary vehicle for software delivery.
At the start of the year, companies love “the kick off.” We discuss how to best take advantage of these events, aside from drinking. Coté also reviews the Apple Watch, and we discuss a smattering of tech world news.
SPONSOR: Take our awesome, multi-cloud PaaS for a test-ride. Get two free months of Pivotal Web Services. Whether you want to deploy on-premises, in a dedicated public cloud, or just keep using our PaaS, Pivotal Cloud Foundry has everything you need for doing cloud-native applications. Go to cote.io/pivotal for the sign-up code!
Oracle buys Austin-based StackEngine – DOCKER DOCKER DOCKER – Raised $4.5 million and sold for $1.3? 5ish people – I love the “I don’t know, it’s some nerd shit” tone of coverage here, e.g., “And then when the developer sends the app to the cloud, it sends it to a Docker container running on a cloud, and all that stuff just works, no troubleshooting.”
Meanwhile: Austin Docker Meetup – Coté on panel with some other folks. Much interest in the crowd (60-80 people for an Austin meetup!). Questions around security, the two standards group. See Coté’s industry data round-up, mostly from DataDog and New Relic, but a 451 cameo. Industry analysts have very little quantitative data on Docker/containers.
Ernest Mueller has helped introduce DevOps in several organizations and has been talking about those stories at two companies he’s worked for, National Instruments and BazaarVoice. Matt and Coté hear these stories (mostly at National Instruments) and we discuss how Ernest and others helped transform these companies to the new way.