Draft: Archiving blog post #4928
Conversation
Deploying eventstore with
|
| Latest commit: |
e9b4e72
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://4a01682f.eventstore.pages.dev |
| Branch Preview URL: | https://archiving-blog-post.eventstore.pages.dev |
Qodana for .NETIt seems all right 👌 No new problems were found according to the checks applied 💡 Qodana analysis was run in the pull request mode: only the changed files were checked Contact Qodana teamContact us at [email protected]
|
| @@ -0,0 +1,248 @@ | |||
| # Archiving: Hands on! | |||
There was a problem hiding this comment.
I think somewhere we should mention that archiving is simple to configure and use. There's no specialness about archived data from the client point of view - it reads like any other data, just a bit slower due to the latency of the underlying object store. This isn't just a cost play - it's also a scalability play and is really the foundation of separating storage from compute for KurrentDB.
| - How do I determine proper values for the retention policy? | ||
| - How do I scavenge the archive? | ||
| - How do backups work? | ||
|
|
There was a problem hiding this comment.
Should we have a part 2 blog post that goes into these details? I understand that they are in the documentation, but this may be useful content to also surface in another blog post as well.
No description provided.