How does Catalyst's state management differ from Restate's virtual objects for durable execution?

Restate uses virtual objects with built-in state management, treating state as a first-class primitive within its durable execution model. Catalyst separates concerns: Dapr Workflows handle durable execution, while state is managed via Dapr's state management building block (e.g., Redis, SQL Server). This gives you flexibility to choose your state store and lifecycle, but adds configuration effort. If you want state tightly coupled to workflow logic with minimal setup, Restate is simpler. Catalyst suits teams needing separate state backends for compliance or multi-region replication.