Just released: github.com/tonbo-io/typ.... When working with arrow-rs, we noticed that schemas are declared at runtime. typed-arrow provides pure compile‑time Arrow schema declaration:
✅ No runtime errors
✅ No runtime overhead
Heavily using Rust macros and abstract type system.
✅ No runtime errors
✅ No runtime overhead
Heavily using Rust macros and abstract type system.
August 18, 2025 at 1:17 PM
Just released: github.com/tonbo-io/typ.... When working with arrow-rs, we noticed that schemas are declared at runtime. typed-arrow provides pure compile‑time Arrow schema declaration:
✅ No runtime errors
✅ No runtime overhead
Heavily using Rust macros and abstract type system.
✅ No runtime errors
✅ No runtime overhead
Heavily using Rust macros and abstract type system.
Refactoring code with Cursor is akin to static program analysis followed by optimizations for performance or readability. It would be fantastic if agents could leverage runtime information in just-in-time automatic coding tasks.
June 15, 2025 at 12:08 PM
Refactoring code with Cursor is akin to static program analysis followed by optimizations for performance or readability. It would be fantastic if agents could leverage runtime information in just-in-time automatic coding tasks.
LSM Tree pushes lots of works to background and improves data writing. However, it is not easy to create and manage background tasks in the browser, this limits the usage of LSM Tree based DB in the browser. We explored the practice of threads in WASM:
tonbo.io/blog/threads...
tonbo.io/blog/threads...
January 20, 2025 at 7:41 AM
LSM Tree pushes lots of works to background and improves data writing. However, it is not easy to create and manage background tasks in the browser, this limits the usage of LSM Tree based DB in the browser. We explored the practice of threads in WASM:
tonbo.io/blog/threads...
tonbo.io/blog/threads...
IMO tradisional Chinese is the real point-free style, let's define:
各(each): (a -> b) -> [a] -> [b]
加(+): int -> int -> int
一(one): int
于(at): .
相(fold0): (a -> b -> b) -> [a] -> b
相加于各加一 `fold0 (+) . map (+1)` is also a natural chinese sentence and a valid function, it shows the composability
各(each): (a -> b) -> [a] -> [b]
加(+): int -> int -> int
一(one): int
于(at): .
相(fold0): (a -> b -> b) -> [a] -> b
相加于各加一 `fold0 (+) . map (+1)` is also a natural chinese sentence and a valid function, it shows the composability
December 31, 2024 at 4:13 AM
IMO tradisional Chinese is the real point-free style, let's define:
各(each): (a -> b) -> [a] -> [b]
加(+): int -> int -> int
一(one): int
于(at): .
相(fold0): (a -> b -> b) -> [a] -> b
相加于各加一 `fold0 (+) . map (+1)` is also a natural chinese sentence and a valid function, it shows the composability
各(each): (a -> b) -> [a] -> [b]
加(+): int -> int -> int
一(one): int
于(at): .
相(fold0): (a -> b -> b) -> [a] -> b
相加于各加一 `fold0 (+) . map (+1)` is also a natural chinese sentence and a valid function, it shows the composability
Merry Christmas!!! and guess what's inside the box?
December 25, 2024 at 5:04 AM
Merry Christmas!!! and guess what's inside the box?
Simply listing the I/O requirements for building a log-structured DB on S3:
- Manifest: Stored as logs, requiring sequential writes.
- SSTable: Full-writes work fine with S3.
- WAL: Stored as logs, requiring sequential writes.
I really wish sequential writes were better supported.
- Manifest: Stored as logs, requiring sequential writes.
- SSTable: Full-writes work fine with S3.
- WAL: Stored as logs, requiring sequential writes.
I really wish sequential writes were better supported.
December 22, 2024 at 7:04 AM
Simply listing the I/O requirements for building a log-structured DB on S3:
- Manifest: Stored as logs, requiring sequential writes.
- SSTable: Full-writes work fine with S3.
- WAL: Stored as logs, requiring sequential writes.
I really wish sequential writes were better supported.
- Manifest: Stored as logs, requiring sequential writes.
- SSTable: Full-writes work fine with S3.
- WAL: Stored as logs, requiring sequential writes.
I really wish sequential writes were better supported.
A time-series database is essentially a HSAP database, as it needs to handle both real-time point queries for monitoring in observability use cases and offline range queries for tasks like historical analysis and AIOps training.
December 18, 2024 at 11:24 AM
A time-series database is essentially a HSAP database, as it needs to handle both real-time point queries for monitoring in observability use cases and offline range queries for tasks like historical analysis and AIOps training.
People always ignore that Box equals to Box in Rust, I ran into this issue again: github.com/apache/arrow...
November 18, 2024 at 4:52 PM
People always ignore that Box equals to Box in Rust, I ran into this issue again: github.com/apache/arrow...
🚀 In the next release, Tonbo will support browser deployment with WASM. As the first step, Fusio is taking a big step forward with OPFS support—perfect for those needing a virtual file system that bridges local disk and S3 access right in the browser. Dive in the preview here: t.co/KCM5jPS3jW
https://github.com/tonbo-io/fusio/tree/4ff969d4c4d7f6a28d696aeb1b62cbeb0260d931/examples/opfs
t.co
November 9, 2024 at 8:25 AM
🚀 In the next release, Tonbo will support browser deployment with WASM. As the first step, Fusio is taking a big step forward with OPFS support—perfect for those needing a virtual file system that bridges local disk and S3 access right in the browser. Dive in the preview here: t.co/KCM5jPS3jW
Fusio released 0.3.0, in which read and write semantics migrated to "exactly read at" and "truncate to 0 and append to". Compare with standard file op, random read and sequential write are more useful in DB scenarios and also suitable for io_uring. check it out: docs.rs/fusio/latest...
Read in fusio - Rust
The core trait for reading data, it is similar to `std::io::Read`, but it takes the ownership of the buffer, because completion-based IO requires the buffer to be pinned and should be safe to cancella...
docs.rs
October 25, 2024 at 3:21 PM
Fusio released 0.3.0, in which read and write semantics migrated to "exactly read at" and "truncate to 0 and append to". Compare with standard file op, random read and sequential write are more useful in DB scenarios and also suitable for io_uring. check it out: docs.rs/fusio/latest...