In this episode, Rick and I discuss something I've been thinking about recently: kubernetes as an enterprise architecture. As we open up with, kubernetes people like to call it an "API," which always seems weirds to me as a former programmer. But, there's something important that they're getting to: a standard set of interfaces, processes, and data formats that comes together to define a programming and operations model. You know: an enterprise architecture. Also, Rick tell us what his weird Twitter handle means.

In this episode, Rick and I discuss something I've been thinking about recently: kubernetes as an enterprise architecture. As we open up with, kubernetes people like to call it an "API," which always seems weirds to me as a former programmer. But, there's something important that they're getting to: a standard set of interfaces, processes, and data formats that comes together to define a programming and operations model. You know: an enterprise architecture. Also, Rick tell us what his weird Twitter handle means.

Sometimes you feel like a microservice, sometimes you feel like a monolith. In this episode, Coté talks with Nate Schutta about his new book Responsible Microservices: when to use them, when to use a service mesh, the (false?) hope of polyglot programming, monolithic shaming, and giant zucchinis.

Sometimes you feel like a microservice, sometimes you feel like a monolith. In this episode, Coté talks with Nate Schutta about his new book Responsible Microservices: when to use them, when to use a service mesh, the (false?) hope of polyglot programming, monolithic shaming, and giant zucchinis.

This year's SpringOne conference is packed with great talks. In this episode, Rita and Coté tell you their picks. Go to SpringOne.io to register and attend for free!

This year's SpringOne conference is packed with great talks. In this episode, Rita and Coté tell you their picks. Go to SpringOne.io to register and attend for free!

In part one, Rohit showed how to analyze and sort an application portfolio to find apps that should be modernized first. In part two, we discuss the process of breaking down a monolith. It starts by making sure that everyone agrees on goals and objects.

In part one, Rohit showed how to analyze and sort an application portfolio to find apps that should be modernized first. In part two, we discuss the process of breaking down a monolith. It starts by making sure that everyone agrees on goals and objects.