Thanks for taking a look. Yes, I kept it closed source for now. I'll mention that on the page.
Litestream with SQLite would solve some of these use cases, and backing up to S3 or GCS works well.
Here I was focused on more dynamic workloads. For example, larger indexes and corpus that can be accessed by multiple readers. I didn't want to invest in local storage, so the data is made to stay cold until it's actually accessed into warm cache.
Also, one node can serve all of that in one collection while serving typed agent memory in another.
Perhaps I missed something, but storage, memory, and operational overhead is something I wanted to worry less about.
alt Hacker News
Thanks for taking a look. Yes, I kept it closed source for now. I'll mention that on the page.
Litestream with SQLite would solve some of these use cases, and backing up to S3 or GCS works well.
Here I was focused on more dynamic workloads. For example, larger indexes and corpus that can be accessed by multiple readers. I didn't want to invest in local storage, so the data is made to stay cold until it's actually accessed into warm cache.
Also, one node can serve all of that in one collection while serving typed agent memory in another.
Perhaps I missed something, but storage, memory, and operational overhead is something I wanted to worry less about.