agavra

6 ms·

1. 31.▲
   by agavra 10mo ago

   Sounds like a perfect fit for https://slatedb.io/ -- it's just that (an embedded, rust, KV store that supports transactions). It's built specifically to run on object storage, currently relies on the `object_store
2. 32.▲
   Frameworks for Understanding Databases(bitsxpages.com)

   3 points by agavra 10mo ago|0 comments
3. 33.▲
   Writing a Time Series Database from Scratch (2017)(web.archive.org)

   1 points by agavra 1y ago|0 comments
4. 34.▲
   Show HN: Imprint – Serialization Format for Data Pipelines(github.com)

   1 points by agavra 1y ago|0 comments
5. 35.▲
   Kafka Streams Cost Calculator(kafkastreams.money)

   3 points by agavra 2y ago|0 comments
6. 36.▲
   If not RocksDB, then what? Why SlateDB is the right choice for Stream Processing(responsive.dev)

   4 points by agavra 2y ago|0 comments
7. 37.▲
   So You Want to Write a Stream Processor? Beware of the Duck Syndrome(responsive.dev)

   4 points by agavra 2y ago|0 comments
8. 38.▲
   Stream Processing Is More Ubiquitous Than You Think(twitter.com)

   3 points by agavra 2y ago|0 comments
9. 39.▲
   Introducing Responsive(responsive.dev)

   12 points by agavra 3y ago|0 comments
10. 40.▲
    How do you change a never ending query?(confluent.io)

    3 points by agavra 5y ago|0 comments
11. 41.▲
    by agavra 5y ago

    There's a whole class of interesting problems related to query evolution - and it varies greatly depending on the "environment" that you're interested in (see mjdrogalis' docs on updating a running query). Generally