Going stateless with authorization-as-a-service (Ep. 559)

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.

Episode notes:

Cerbos is an open-source, scalable authorization-as-a-service that aims to make implementing roles and permissions a cinch. Explore their docs or see how their customers are using Cerbos. 

Stateless applications like Cerbos don’t retain data from previous activities, giving devs predictable plug-and-play functionality across cloud, hybrid, on-prem, and edge instances.

Connect with Alex on LinkedIn and Twitter.

Shoutout to Lifeboat badge winner Hoopje for rescuing Print in bold on a terminal from the dustbin of history.

TRANSCRIPT

The post Going stateless with authorization-as-a-service (Ep. 559) appeared first on Stack Overflow Blog.

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.

Episode notes:

Cerbos is an open-source, scalable authorization-as-a-service that aims to make implementing roles and permissions a cinch. Explore their docs or see how their customers are using Cerbos. 

Stateless applications like Cerbos don’t retain data from previous activities, giving devs predictable plug-and-play functionality across cloud, hybrid, on-prem, and edge instances.

Connect with Alex on LinkedIn and Twitter.

Shoutout to Lifeboat badge winner Hoopje for rescuing Print in bold on a terminal from the dustbin of history.

TRANSCRIPT

The post Going stateless with authorization-as-a-service (Ep. 559) appeared first on Stack Overflow Blog.

 se-stackoverflow, se-tech, The Stack Overflow Podcast, authorization-as-a-service, microservices, stateless, the stack overflow podcast 

Author: 010

Leave a Reply

Your email address will not be published. Required fields are marked *