In preparation for his DevOpsDays Atlanta talk, Josh and Coté (well, mostly Coté) talk about the relationship between microservices and DevOps. They use the CAMS framing to go over how microservices could provide the architectural requirements to make DevOps possible.
Having something to sell is always key to a profitable business. We explore this life-hack of the business world in discussion Twitter and then Amazon licensing Thursday night football. There’s also some brief talk of Akamai buying SOASTA, Cloudera filing to IPO, and the lost dichotomy of agent/agentless.
What does it really mean to “run like Google”? Is that even a good idea? Andrew Shafer comes back to the podcast to talk with Coté about how the Google SRE book and the newly announced Google CRE program start addressing those questions. We discuss some of the general principals, and “small” ones too that are in those bodies of work and how they represent an interesting evolution of it IT management is done. Many of the concepts that the DevOps and cloud-native community talks about pop in Google’s approach to operations and software delivery, providing a good, hyper-scale case study of how to do IT management and software development for distributed applications. We also discuss Pivotal’s involvement in the Google CRE program.
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.
While it’s unknown how much time you should let your kids play Minecraft, it’s equally unclear at the moment who’ll win the second cloud wars. Between Google, Azure, AWS, and all the others, how companies differentiate themselves and what customers will buy on isn’t sorted just yet. We discuss Google Next, Pivotal’s momentum announcement, and serious theories for Okta IPO’ing.
I did this podcast with my friend Charles Lowell from about 2005 to probably about 2012 or 2010. Once we got big boy jobs and kids, we dropped off, though we went to do other podcasts: Charles has the Frontside podcast, and I have all sorts of other ones.
Every now and then since then we’ve put one out, but really, not that often.
There’s tell that some people just look at containers as a cheaper way to virtualize, eschewing the fancy-lad “cloud-native stuff.” We discuss that idea, plus “the enterprise cloud wars,” and also our feel that Slack is actually a really good tool and company.
Whether it’s “DevOps,” “digital transformation,” or even “cloud” and “agile,” middle-management is all too common an issue. They simply won’t budge and help out. This isn’t always the case for sure, but “the frozen middle” is a common problem.
With a big ol’ panel of people (including two folks from RedMonk), we talk about tactics for thawing the frozen middle.
We’ve got all your answers to “what exactly is ‘cloud-native’?” in this episode with special guests Pivotal’s Kenny Bastani and RedMonk’s James Governor. Kenny gives us a good overview of what cloud-native is, as Coté summarizes it: handling the configuration and automation for your applications along with all the supporting frameworks and platforms to do that. We then discuss the process (“culture”) angle, the origin of Spring Boot, the concept of “lock-in,” and if public cloud is needed or not. Bonus: serverless talk!
In this week’s episode, Richard and I talk with Dino about the work Pivotal does to help companies quickly start migrating applications to Pivotal Cloud Foundry. Check it out, and subscribe if you haven’t already.
Another interview, mostly on cloud and other dorky topics:
Having worked in cloud since before cloud, JJ and I talk about what companies are using various cloud things for. We also discuss the conceptual history of cloud, and what exactly he does as a “business development” person at Chef.
Snap is looking to spend billions on AWS and Google Cloud over the next five years. We talk about what exactly that could be for, then check in with Google’s social strategy and thermostat strategies; meanwhile, the America Fuck Yeah crew wants to start gathering passwords at the boarder. Also, Brandon lays out the case that an open-core monitoring startup is a hard row to hoe.Also, Baltimore is not in Maine. (But Coté is pretty sure it actually is.)
During a spate of Pivotal Conversations podcast recordings I had the change to quickly talk with RedMonk’s Rachel Stephens about financials, something she knows plenty about. She gave some handy tips on how to read them. Check out the interview, subscribe to the podcast!
What’s the best way to categorize and prioritize your IT projects? Splitting them up between systems of record (ERP) and systems of engagement (user-facing apps) is a popular mode of thinking, highly related to bi-modal IT. In this episode, guest Ian Andrews explains why this framing is a bad idea and offers a value-driven way of thinking about it instead, along with plenty of commentary from Coté and Richard.
While in San Francisco for a Pivotal meeting, I recorded an episode with Josh Long. We talk about what reactive programming is and why you’d use it. Also, dish towels. Also, check out the livestream of this if you’re into video.
How do containers fit into your cloud native planning? That’s a the question we start with this week, with (returning guest) John Feminella. We quickly arrive at a conversation on the larger question which is how to build a cloud platform and the allure of building it yourself. Also, we cover recent news in the infrastructure software space.
One of your favorite technologies is on the death wagon, again. Gartner recently recommended avoiding JEE for new, cloud native application development. This predictably kicked up all sorts of push-back from the JEE stalwarts. In this episode we discuss the report, the responses, and all the context to figure out what to make of all this. Spoiler: JEE isn’t dead, as ever, it’s just a part of the ongoing gumbo that is a Java application.
Apple has put out three new things – the phone, the watch, and the OS – which we discuss. And then Oracle announced it’s destroying Amazon, which is fun. We start it all off with a word-salad of the usual nonsense and deodorant talk.
There’s also the annual vBBQ event, Oct 17th at the Salt Like. Pivotal is sponsoring (check out my CORPORATE AMEX, BITCHES!). Come to it, it’s mostly free-ish.
For more DevOps awesomeness, join the Chef Community Summit, October 26th and 27th in Seattle, WA. This Open Space event provides a great opportunity to connect with the DevOps Community and Chef Engineers over two days of engaging sessions and hallway discussions. Bring your ideas, passion and excitement for Chef and DevOps to this highly interactive event. Go to summit.chef.io to register for this awesome event and use the code PODCAST to get 10% off your ticket!
It’s all fundings, divestitures, and acquisitions this week. Hashicorp gets some cash, HPE sells off it’s software group to Micro Focus, and Google buys Apigee…plus Twitter acquisition rumors. Plus sentient carpets.
“HPE will be retaining tools that support the company’s cloud and infrastructure businesses but will be spinning off tools for application delivery management, big data, enterprise security, information management, governance and IT operations management.”
From what I know of HPE, this seems to be overlapping. I’d love a list of “stays vs. goes”
Q3 2017, and you thought Dell/EMC was slow
Where does this leave HP? Will they acquire more SW or stay a “systems” company.
It makes you realize how “small” their SW group was.
For more DevOps awesomeness, join the Chef Community Summit, October 26th and 27th in Seattle, WA. This Open Space event provides a great opportunity to connect with the DevOps Community and Chef Engineers over two days of engaging sessions and hallway discussions. Bring your ideas, passion and excitement for Chef and DevOps to this highly interactive event.
Go to summit.chef.io to register for this awesome event and use the code PODCAST to get 10% off your ticket!
Google buying Apigee. The whole API Economy thing.
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.
This week we discuss Rackspace going private and the OpenStack cloud scenarios that could have been. We also cover Matt Ray’s first trip to New Zealand where, sadly, he finds no Power Ranger monuments. Also, a little bi-modal flavor for ya.
Check out the full show notes (https://cote.io/sdt70) for links to the recommendations, conferences, and tech news items we didn’t get to cover.
“MSPs need to work with customers to convert their infrastructure to Platform-as-a-Service using microservices architecture,” said one AWS partner. “They also need to bring DevOps into the heart of the organization. Unfortunately, most MSPs don’t have the developers that truly understand this.”
“Few AWS Partners Are Really Surprised By Sentinel’s Emergence“
There’s always good food in the enterprise sales meeting racket: gourmet pimento cheese, sushi and sake, and booze. Also, the Gartner magic quadrant for IaaS in out, which we discuss. With layoffs at Cisco we look at the broader numbers around layoffs in the tech sector. Before recommendations we briefly talk about Walmart buying Jet.
“I do not think that they are going to be done after this.”
“We are committed to making the necessary decisions to drive our future growth”
The performance didn’t impress investors as Cisco’s stock shed 42 cents to $30.30 in extended trading after the numbers came out. The decline may have been driven by disappointment that Cisco’s job cuts weren’t nearly as deep as published reports had speculated they would be.
“I get to see your face during this podcast,” Matt says as we start talking about SpringOne Platform. Both of us were there and we recap Matt’s talk on managing 10 Pivotal Cloud Foundry instances, namely, how they figured out using a Concourse pipeline to automate much of that management. We discuss “how to do the transformation” talks we liked, like the Citi talk.
In addition to some other random digital transformation topics, we also discuss how HR policies are struggling to change with things like pair programming and DevOps.
While at SpringOne Platform I’ve been recording some Pivotal Conversations podcasts: here’s one with Josh McKenty on the Pivotal ecosystem and a bit on using OpenControl for automating compliance. One of the industry nuggets that’s interesting in that is how a die-hard agile company like Pivotal has to adapt how it works with less agile companies. The discussion role of systems integrators is interesting as well.
I’ve had a theory that the hard-line philosophy of open source has softened in recent times. Rather than thinking closed source is to be avoided at all costs, I think most developer types are a lot more willing to accept closed source bits mixed in with open source bits. That is, open core has “won.” I discuss this topic with my long time pal, Barton George, while at SpringOne Platform, plus the work he’s doing in the developer and OSS worlds at Dell.
This week, Richard and I talk about the full, end-to-end process of doing software. Plus, we cover some recent cloud native news:
When you put all of the step needed to create good software up on the board, there’s a lot of them. It’s a lot more than just writing code, or even writing requirements and stories. Around Pivotal, we think of this full, end-to-end process as the circle of code: Ideas → prioritization / planning → coding → deployment → runtime → monitoring → feedback, and back again. Richard and Coté discuss these steps and how organizations are starting to appreciate “the big picture.” They also cover some cloud native news: Amazon buying a browser-based IDE, Cloud9; Google expanding their cloud; and Verizon’s purchase of Yahoo!
We’ve seen a goodly spate of news in the container space recently which we cover in the episode. In the second half, we talk with Kevin Hoffman about the .NET world, Steel Toe, and his book, Beyond the Twelve-Factor App. A recent survey from the Cloud Foundry Foundation is widening the framing around container management, adding in the use of Platform-as-a-Service into the usual container orchestration mix. The survey also shows some interesting results around adoption, e.g., managing containers in production ends up being more difficult than people predict during evaluations. Also since our last episode, DockerCon brought a bevy of announcements in the container ecosystem which we cover briefly. And highly relevant to our guest, Kevin Hoffman, .NET Core 1.0 was officially released, as open source. In the second half we talk about the recent history of .NET and how it’s being used to create microservices. We also talk about the three extra “factors” Kevin’s book adds to the 12 factor app and typical experiences when migrating to 12 factor apps.
Is anyone minding the business side of these container orchestration plays? That’s the main topic we discuss after doing over recent Docker announcements. We then discuss the state of tech journalism and throw out a free business plan for left-ish fried chicken slinging.
If you chose a provider, you do not get to just point your finger at them in the post mortem and say it’s their fault. You chose them, it’s on you. It’s tacky to blame the software or the service, and besides your customers don’t give a shit whose “fault” it is.
You’ve heard of “analysts,” those people who cover the technology world with all sorts of quadrants, waves, and forecasts about how much money is spent on different types of software. What industry analysts do is actually a long, interesting list depending on who you are, their customer: a buyer and user of IT, financial and investment banker types, or vendors. This week, after a small section of new left over from last week – are you keeping up here? – we interview Rita Manachi, head of analyst relations at Pivotal. We ask her to go over what analysts do and her tips on working with them.
With two surprise acquisitions this week we have a lot of synergies to discuss. We cover Samsung picking up Joyent, and Microsoft buying LinkedIn. Highly related is a recent article trying to explain what’s going on with private equity buying tech companies. Then, we discuss the big news from chef we’ve been waiting for: the announcement of habitat.
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/sdt66.
Login with LinkedIn + AD = SSO won. Also: “Massively scaling the reach and engagement of LinkedIn by using the network to power the social and identity layers of Microsoft’s ecosystem of over one billion customers. Think about things like LinkedIn’s graph interwoven throughout Outlook, Calendar, Active Directory, Office, Windows, Skype, Dynamics, Cortana, Bing and more.”
“Along with the new growth in our Office 365 commercial and Dynamics businesses this deal is key to our bold ambition to reinvent productivity and business processes.” (MSFT CEO, from MSFT internal memo)
Ads and dumb-AI context: “This combination will make it possible for new experiences such as a LinkedIn newsfeed that serves up articles based on the project you are working on and Office suggesting an expert to connect with via LinkedIn to help with a task you’re trying to complete. As these experiences get more intelligent and delightful, the LinkedIn and Office 365 engagement will grow. And in turn, new opportunities will be created for monetization through individual and organization subscriptions and targeted advertising.” (MSFT CEO, from MSFT internal memo)
LinkedIn growth since Dec, 2008: “Our team has grown from 338 people to over 10,000, our membership from 32M to over 433M and our revenue from $78M to over $3 billion.” (MSFT internal memo).
Others from memo: Lydia training inline in MSFT apps; paid content in MSFT apps (a la Spiceworks); HR and recruiting.
Deal PR deck – pretty good. I can see how the social graph and all the “semantic web sit” in LinkedIn, crossed with MSFT assets works well.
I-banker stuff: “Microsoft will pay $196 per share to acquire LinkedIn, a 50% bump up from where it was trading ahead of the deal announcement, although well behind the $250 each share was worth in November. The price tag values LinkedIn at 8.2x trailing revenue.”
“The company [Microsoft] must find new ways to differentiate. Integrations with LinkedIn offer potential functionality that will be challenging to duplicate. When the two companies are joined, there will be multiple ways that LinkedIn’s member network, and the data from that, will go into improving Microsoft’s Office and Dynamics apps, besides the other benefits from running a combined company.”
“LinkedIn’s tools for recruiters account for 58% of the $860m in revenue it generated in the first quarter of the year [so, $3.440bn run rate]. When combined with educational material from its Lynda.com acquisition, HCM tools make up 65% of sales. Tools for marketers and premium subscriptions (including its offering for sales teams) each make up less than 20% of the business, and are the slowest growing parts of the business.”
“Microsoft is the world’s largest software developer, with about $100bn in sales and a $400bn market cap.”
The theory seems to be: SaaS companies are undervalued, and PE firms are looking to buy cheap assets and grow them, and re-exit them. This vs. the usual cut costs and re-exit then. Of course, Qlik and Ping aren’t SaaS.
Habitat centers application configuration, management, and behavior around the application itself, not the infrastructure that the app runs on.
Habitat is comprised of plan and build system, a supervisor, an HTTP interface on that supervisor to report package status, a depot, a communication model for disseminating rumors through a supervisor ring, and many other components.
“Greene is also tapping her VMware Rolodex, talking with big enterprise rivals like SAP SE, Microsoft and Oracle, to get more of their products into the Google cloud. That’s must-have for some large companies, which need prepackaged software from these providers to run their businesses. No Oracle or SAP products are available on Google’s cloud today. Microsoft and Oracle declined to comment, while SAP confirmed early talks.” From Jack Clark’s Bloomberg piece.
We spend this week talking about workload scheduling, starting with Mesos. It’s a fun ride from CONTROL-M to Lambda, along with Cloud Foundry and serverless. So get ready to beat a horse into glue. Plus, how to handle gifts for father’s day and the usual recommendations at the end.
Check out the full show notes for links to the recommendations, conferences, and tech news items we didn’t get to cover.
Heron is a newly open-sourced replacement for Storm. Supporting all of our own code isn’t sustainable, need an open source community.
The Ellen Degeneres photo tweet from the 2015 Academy Awards knocked a couple of services over. 25% traffic spike, hit 255k/tweets per second. 2016 Academy Awards had 2x the traffic, no failures.
30,000 node Mesos cluster (probably largest). “We don’t like being the biggest of anything, we find the edge cases.” 130,000,000 containers launched daily.
Some of their acquisitions were in public cloud, they don’t move them in-house. They’re actually pushing new services out to AWS where they can. Vine, TellApart, Crashlytics, MoPub, BlueFin, etc. Ad-serving is mostly in AWS.
Users: Time Warner, Twitter (30,000 host deployment), Apple Siri.
Maybe Brandon can regale us with some history: tales of The Mercury Wars!
Also, some ALM stuff. Sadly, I don’t have access to the IDC reports on this, however, they’re expecting big things: “IDC’s analysis of this market resulted in worldwide agile application life-cycle management software 2014 revenue of $450.3 million, up 30.5% from the 2013 revenue of $345 million. IDC expects very strong growth for agile ALM software for the 2014–2019 time frame, with growth to $1.8 billion by 2019 and a high CAGR of 32%”
While Texas moistens up, we talk about the morals of rich tech folks suing journalists, the state of open source business, the history of the BI market, and how to use the Meeker decks. Check out the full show notes for links to the recommendations, conferences, and tech news items we didn’t get to cover.
Software is getting faster at eating the (ecommerce) world: “The time it takes retailers to get to $100 million in online sales is shrinking. It took Nike 14 years from the time its retail site launched, compared to nine years for Lululemon, and eight year for Under Armour.”