Pivotal Podcasts

There are a number of capabilities developers need in order to be successful. One of them is easy and fast access to data. Today more than ever, applications rely on both large scale and high-velocity data pipelines to support key features and capabilities. But with so many applications and microservices requiring data, things can get pretty complex pretty quickly. There needs to be a way to tame this complexity so developers can do their best work. In this week's episode of Pivotal Insights, hosts Jeff Kelly and Dormain Drewitz speak with Shawn McAllister, CTO at Solace Systems. Solace is a provider of open data movement solutions and a Pivotal partner. The three discuss some of the challenges developers face building data pipelines and messaging queues in cloud-native environments, highlight some speccific use cases like data movement for IoT applications, and explore how developers can leverage Solace on Pivotal Cloud Foundry.

Turns out there's a lot more to building a strong partner ecosystem that delivers real value to customers than just putting out joint press releases with lovey-dovey language, a.k.a. Barney press releases. Luckily, that's the type of work Pivotal is putting in with partners across the Cloud Foundry ecosystem. In this episode of Pivotal Insights, Dormain and Jeff talk about what it means to put customers first and the importance of a vibrant ecosystem. They also discuss enterprises making the transition to software-driven. As an added bonus, Dormain shares some insights on ancient Roman festivals.

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. See full show notes at http://pivotal.io/podcast

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 princiapls, 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 distrbuted applications. We also discuss Pivotal's involvement in the Google CRE program. See full show notes at http://pivotal.io/podcast

In this episode, Richard and Coté talk with Dieu Cao, the Elastic Runtime PMC, about how work on the open source Cloud Foundry code base works, prioritizing features, and some of the projects she works on like isolation segments. While we have her, we also talk about the naming schemes of Cloud Foundry components and the evolution of QA from way back in Dieu's early days as a tester. Our short news segment goes over Microsoft buying Deis and some cloud spending indicators around public cloud capital expenditures and bank's need to rewrite piles of COBOL. Full show notes: http://pivotal.io/podcast

One of the fundamental tenants of twelve-factor applications is that developers shouldn’t have to concern themselves with the underlying complexities of the infrastructure supporting their apps. This goes for dealing with how 12 factor apps communicate with each other. Spring Cloud Stream helps mitigates this challenge, whether you’re using RabbitMQ, Kafka, Google pub/sub or any other messaging tool. “With Spring Cloud Stream, the messaging middleware will not behave the same, but your application will work the same,” said Marius Bogoevici, the project lead for Spring Cloud Stream at Pivotal. In this episode of Pivotal Insights, host Jeff Kelly speaks with Marius about the challenges associated with developing message-driven microservices in cloud-native environments, how Spring Cloud Stream lets developers focus on building software that benefits the business, and how Pivotal customers are putting Spring Cloud Stream to work in the enterprise.

There's a handful of cloud news to go over - AWS S3 going down, Google's new database, Spanner, and others. We then discuss some ideas for how enterprise architects can help out in a cloud-native organization. Then, we discuss Coté's new project, tactical advice for organizations who are finding it difficult to do all the right things that DevOps and cloud-native think prescriptions. See the work in progress at http://cote.io/cloud3. See full show notes at http://pivotal.io/podcast.

We talk about the traditional and new relationship between data and application development, and, now, DevOps. The world of databases, data warehouses, and other DBAs is not starting to collide with DevOps. In this episode, we talk with Dormain Drewitz, Stephen O’Grady, and Kenny Bastani about the evolving role of data in DevOps-think. See full show notes: http://pivotal.io/podcasts

Microservices provide a number of benefits to developers and, ultimately, end-users of applications supported by microservices architectures. These include the ability to scale and develop each microservice independently, which enables increased release velocity. But microservices also introduce a number of challenges that developers need to address, especially if they are developing mission-critical transactional applications. Among these challenges is maintaining data consistency across a set of microservices. Enter command query responsibility segregation, or CQRS. In this episode of Pivotal Insights, host Jeff Kelly dives into the topic of CQRS with Pivotal's own Kenny Bastani. Kenny, a Spring developer advocate, lays out the challenges CQRS helps microservices developers overcome, provides advice for implementing CQRS, and discusses the complexities that CQRS itself introduces to microservices applications.

There was a time when the only people concerned with application performance were operations teams. And maybe the enterprise users frustrated by slow app performance. But today, anyone interested in the the performance of their business should be interested in the performance of their applications, says Abner Germanow. Germanow, who is Senior Director of Strategic Marketing and Campaigns at New Relic, says that now more than ever application performance has a direct impact on customer interactions, revenue generation and the overall performance of the business. In this week's episode of Pivotal Insights, host Jeff Kelly and Germanow discuss the evolving role of application performance monitoring (APM) in cloud-native environments, the impact of microservices and DevOps on APM, how data is the great equalizer in ensuring application performance, and how Pivotal and New Relic are helping joint customers keep their cloud-native applications humming.

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! Full show notes and more at: http://pivotal.io/podcast

When you think about microservices, you probably think of open-ended services supporting user facing applications like Netflix or Uber. These services must be "always-on." There's no finish line. Some call these streaming services. But not all microservices fall into this category. Some microservices are finite - they have a beginning and a definitive end. Microservices supporting batch data integration jobs fall into this category. So do those supporting database migrations. These microservices shut down after the job is accomplished. Finite microservices like these have their own set of development and deployment requirements and challenges that set them apart from streaming microservices. In this episode of Pivotal Insights, host Jeff Kelly speaks with Michael Minella, project lead for Spring Cloud Task at Pivotal. The two discuss what differentiates finite microservices from their streaming counterparts, identify the unique challenges associated with developing and deploying them, and offers tips for overcoming these challenges with Spring Cloud Task.

Improving how you do software requires changing how every layer your organization's functions day-to-day, from executive leadership, to middle-management, and staff. Often, middle-management is resistant to change and acts as a "frozen middle," slowing and sabotaging leadership and staff's desires to change. Along with Pivotal's Dormain Drewitz, we're joined by RedMonk's Rachel Stephens and Stephen O'Grady to discuss this frozen middle problem and tactics to thaw it. See full shows and more at http://pivotal.io/podcasts

Once you have your shiny new Pivotal Cloud Foundry instance installed, it's time to start selecting new applications to build and existing applications to migrate. Many of this second bucket will be "legacy" applications that aren't immediately compatible with the cloud native approach. Dino Cicciarelli and his team work with Pivotal customers to navigate through this process. We talk about the common process, roadblocks, and mental shifts people go through to be successful. One of the chief thought-technologies deployed is to start working on real, actual applications rather than inflicting a long process of analysis paralysis on yourself. We also cover a sampling of recent news: Visual Studio and Cloud Foundry, patent troll protection in Azure, and Snap's whopping spend on public cloud. See full show notes at http://pivotal.io/podcasts

In this episode of Pivotal Insights, Pivotal’s Sina Sojoodi talks with host Jeff Kelly about how Pivotal clients across industries are turning to Spring Cloud Data Flow (SCDF) to do just that. SCDF is an orchestration tool that enables developers to create composable microservices, including streaming and batch data pipelines, and deploy them on the run-time environment of their choice. Sina, the project lead for Spring Cloud Data Flow at Pivotal, and Jeff discuss the tangible benefits SCDF delivers to developers, including improving productivity, and share examples of the types of microservices Pivotal customers are developing and orchestrating with SCDF.