Topic: Marvin AI
Question: How to persist an Applications State beyond the lifecycle of the app
Context:
The documentation demonstrates how to create a todo app and persist information in the apps state. How would an engineer approach expanding that state beyond the lifecycle of the application.
For example if I wanted to always refer to my todo list through many different restarts of the application, what would be the best approach to persisting the state in a db and rehydrating the application with my state
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.