Skip to content

Commit e87808a

Browse files
fixup: blob blog post date (#310)
* fixup: blob blog post date * fixup: add metadata
1 parent 7470204 commit e87808a

File tree

1 file changed

+17
-5
lines changed
  • src/app/blog/blob-store-design-challenges

1 file changed

+17
-5
lines changed

src/app/blog/blob-store-design-challenges/page.mdx

Lines changed: 17 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,15 +4,27 @@ import {ThemeImage} from '@/components/ThemeImage'
44
export const post = {
55
draft: false,
66
author: 'Rüdiger Klaehn',
7-
date: '2025-03-25',
7+
date: '2025-03-12',
88
title: 'Blob store design challenges',
99
description:
1010
"It's just hashed data, what's so complex about a blob store anyway?",
1111
}
1212

1313
export const metadata = {
14-
title: post.title,
15-
description: post.description,
14+
title: post.title,
15+
description: post.description,
16+
openGraph: {
17+
title: post.title,
18+
description: post.description,
19+
images: [{
20+
url: `/api/og?title=Blog&subtitle=${post.title}`,
21+
width: 1200,
22+
height: 630,
23+
alt: post.title,
24+
type: 'image/png',
25+
}],
26+
type: 'article'
27+
}
1628
}
1729

1830
export default (props) => <BlogPostLayout article={post} {...props} />
@@ -34,7 +46,7 @@ So why is designing a blob store for BLAKE3 hashed data so complex? What are the
3446

3547
The job of a blob store is to store two pieces of data per BLAKE3 `hash`, the actual data itself and an `outboard` containing the flattened hash tree that connects each `chunk` of data to the root hash. Data and outboard are kept separate so that the data can be used as-is.
3648

37-
While the [bao] crate stores tree hashes all the way down to &le; 1024 byte BLAKE3 `chunks`, we store the outboard only down to 16 KiB `chunk groups` to reduce the outboard size.
49+
While the [bao] crate stores tree hashes all the way down to &le; 1024 byte BLAKE3 `chunks`, we store the outboard only down to 16 KiB `chunk groups` to reduce the outboard size.
3850

3951
## In memory store
4052

@@ -126,7 +138,7 @@ This is not the end of the world, but it does mean that we need to keep the data
126138

127139
# Blob lifecycle
128140

129-
There are two fundamentally different ways how data can be added to a blob store.
141+
There are two fundamentally different ways how data can be added to a blob store.
130142

131143
## Adding local files by name
132144

0 commit comments

Comments
 (0)