2min chapter

DevOps Paradox cover image

DOP 216: Simplify Microservice Development With Signadot

DevOps Paradox

CHAPTER

The Importance of a Stateful Resource

The idea is you want to be as lightweight as possible. If I've got stateful, going back to your example, I've got two services. They're pointed at a shared database and the data they're accessing has foreign key constraints on each of the tables. To me, that's I need to become a monolith or I need to do a couple of that database. And either answer is okay.

00:00

Get the Snipd
podcast app

Unlock the knowledge in podcasts with the podcast player of the future.
App store bannerPlay store banner

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode

Save any
moment

Hear something you like? Tap your headphones to save it with AI-generated key takeaways

Share
& Export

Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode