InfoQ Homepage PaaS Content on InfoQ
-
Alex Matyushentsev on Argo CD, Argo Rollouts, and Continuous Delivery with Kubernetes
In this podcast Alexander Matyushentsev, principal software engineer at Intuit and core engineer on the Argo CD and Argo Rollouts projects, sat down with InfoQ podcast host Daniel Bryant and discussed the Argo projects, continuous delivery with Kubernetes, and how platform teams can help developers embrace modern release techniques and related technologies.
-
Anubhav Mishra and Nic Jackson on Platforms, Developer Workflows, and HashiCorp Waypoint
In this podcast, Anubhav Mishra and Nic Jackson from HashiCorp sat down with InfoQ podcast host Daniel Bryant. Topics discussed included: the benefits and challenges of creating application platforms in the cloud, the need for effective developer workflows, and the role of the new HashiCorp Waypoint tool and service meshes within workflows
-
Asim Aslam on Microservices, go-micro, and PaaS 3.0
In this podcast, Asim Aslam, founder and CEO of Micro, sat down with InfoQ podcast co-host Daniel Bryant. Topics discussed included: microservices vs functions; the go-micro and micro frameworks; and the evolution of PaaS and how the new M3O platform fits into the landscape.
-
Matthew Skelton and Manuel Pais on Software Architecture, Team Topologies, and Platforms
In this podcast, Matthew Skelton and Manuel Pais, co-authors of the book Team Topologies, sat down with InfoQ podcast co-host Daniel Bryant. Topics discussed included: the role of a modern software architect, how team design impacts software architecture, creating “team APIs” in order to reduce cognitive load, and the benefits of building a “thinnest viable platform”.
-
Dave Sudia on Migrating From a PaaS to a Kubernetes-Based Platform
Daniel Bryant sat down with Dave Sudia, senior DevOps engineer at GoSpotCheck, to discuss the benefits of PaaS; building a platform with Kubernetes as the foundation; selecting open source components and open standards in order to facilitate the evolution of a platform; and why care should be taken to prioritize the developer experience and create self-service operation of the platform.