Solving the data doom loop
Ken Stott, Field CTO of API platform Hasura, tells Ryan about the data doom loop: the concept that organizations are spending lots of money on data systems without seeing improvements in data quality or efficiency.

Ken Stott, Field CTO of API platform Hasura, tells Ryan about the data doom loop: the concept that organizations are spending lots of money on data systems without seeing improvements in data quality or efficiency.
On this episode of the podcast, we talk to Mauricio Linhares, senior software engineer at Stripe, about the pain of migrating monoliths to microservices, defining zero-tier systems, and why plugging all your servers into the same power supply is a bad idea.
The home team welcomes Alex Olivier, cofounder and product lead at Cerbos, for a conversation about how to centralize business logic in a microservices environment, the value of stateless applications, and what’s under Cerbos’s hood.
API gateways, service mesh, and GraphQL, oh my!
Find out about all the features the mesh adds to a service architecture automatically.
The home team sits down with Maxim Fateev, CEO and cofounder of Temporal Technologies, and Dominik Tornow, Principal Engineer at Temporal, to talk all things microservices.
In just 20 years, software engineering has shifted from architecting monoliths with a single database and centralized state to microservices where everything is distributed across multiple containers, servers, data centers, and even continents. Distributing things solves scaling concerns, but introduces a whole new world of problems, many of which were previously solved by monoliths.
Temperature, time, and space. Metric makes it easy to relate them all. Now that's excellent API design.
Sara returns from Miami. The crew chats about Monoliths vs microservices and the lessons we've learned as manager and ICs.