In this episode we talk with Todd Persen on the topic of monitoring cloud-native applications with Pivotal Cloud Foundry Metric. We discuss the changing nature of monitoring in cloud-native platforms, how developers can now turn black-boxes into white-boxes, why time-series dominates the thought-technology in this space now, and the benefits of open source taking over most innovation in systems management. Richard is out this week, so Andrew Shafer returns to fill in as co-host.
There’s a whole slurry of myths about Cloud Foundry. With the platform updating so quickly, many of the issues behind these myths have long been addressed, and many were just false from the get-go. Coté and Richard talk about a recent post dismissing common myths. We also discuss recent news from the infrastructure software world and go over a bunch of upcoming events that Pivotal will be at.
If you use something like Overcast, be sure to check out the overly-extensive chapters and links right inside the podcast.
Container networking and storage is hella-complicated. Check out this conversation with Usha Ramachandran, Richard Seroter, and myself on the topic, including a discussion of why it’s so complicated and how Cloud Foundry addresses the problems.
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.
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.
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.