Відео

Very detailed and to the point discussion. I am in awe as this is just what I needed. Very grateful for this discussion. Thanks for sharing!!

How about to edit/delete a record?

absolute heat, thanks! I'm a big fan of the highlighted subtitles fwiw

Thank you for creating this video Kaivalya! I learned so much about DynamoDB in just 90 minutes from you and Alex. Such valuable insights!

solid, ty! The subtitles came in handy, I was pretty much relying on those when playing at faster playback speeds!

How many parts will be there?

Cool format. Pleasantly surprising how much info you can convey in a fun way in under 20mins.

This is amazing... Keep coming up with more content, especially on Graph Databases

Thank you both for the vid. It's a great discussion. 30:02, Instagram allows user to edit the post dynamic content (description, caption, location, tags, etc)

Awesome explaination 🎉, thanks

He has not spent more time in industry where extremely busy IC schedule open office hours so that their work doesn't get impacted by each and everyone disturbing them.

❤ this content is just awesome

am I the only one questioning how packing 10.000 business transactions into a single DB transaction works consistency wise? :)

Bb

How is Hdfs different from the above mentioned approach?

What is the rust library Simon talked about building flexible storage formats? I heard something like "archive". But failing to find the right one.

These podcasts are goldmine! Also I watched your only livestream today while I was in metro. Got many insights. You should do more livestreams.

Pushing the algorithm ❤

Thanks for updating the video. Great content. Keep it up.

Hi! So, I just integrated DuckDB into my little open source distributed trace viewer and came here to learn more about its internals, but I have to stop the talk for a second and thank you profusely for having clear, amazing subtitles, right in the video. As a programmer with profound hearing loss, it's usually a struggle for me to get through technical videos with the jumpy auto-generated captions UA-cam provides, and it so rare that I get to just sit back and enjoy a talk like a hearing person would. Thank you for providing this experience!

👍

👍

👍

I don't build product directly, but in kind of integration work, but honestly even if I try to think from user perspective, I don't see people around me, in teams, willing to work like that or let others do. 🤣🤣

Nice podcast. Today only I started listening your podcast.

This was awesome!

Heikki rocks!

Your podcasts and the way you dig down to detailed level is revolutionary...please keep making such insightful videos ...this has enhanced my knowledge many folds .. let's catch up if you want

Please remove members only videos. It doesn't make sense yet for your channel.

😅o

The proper way is to rewrite using native languages like C++ or Rust. Use of java again is a plain joke.

Thank you Kaivaly for the video, it was really well explained and the animations are amazing. I would like to point just one thing the title "Reinventing Kafka the right way" I think is not precise once the part that AutoMQ are improving is the Storage Engine system and not the Message Middleware Broker (if I understood correctly based on this video). It was more an opportunity to enhance an isolated component from Kafka for cloud storage instead a full rewrite. An example of "Reinventing the right way" in my point of view would be the ScyllaDB which has backwards compatibility with Cassandra although it was rewritten using C++. I wish the best brow keep going!!!! EDIT 1: And they created a platform over na existent Kafka concept

Great video, learnt a lot!

Thanks for this interview. Great as always! One question: so if the WAL writes are batched and periodically flushed to storage, there in a window in which if the process crashes, the writes will be lost? I.e the client response that write is complete is not durable.

The storage architecture reminds me of AWS RDS (Aurora) Architecture with the control plane managing a muli tenant storage fleet and having write quoram for strong consistency. Great discussion, loved it.

Wonderful video

Information dense conversation! And isn't it expected that size is sufficiently large then it would increase number of put calls to object storage. Why don't you do buffering based on time plus size based criteria?

Thank you for this, looking forward to assisting with the golang port! This was a great overview of the project, and a great way to get acquainted with some of the design decisions.

I love how you simplify complex topics in the crypto space.

Like all duckdb users, I really enjoy hearing Mark Raasveldt talk. You did a great job of guiding the conversation into intesting and informative areas!

This is super cool . Probably the only youtube video [> 1hr ] , which I watched in whole. I took a whole week to watch it ... made sure I understood every idea presented and discussed. Thank you so much. I have a question => The partition placement , is DDB still using consistent hashing , for deciding which partition goes to which node[physical server] ... or there is some other algorithm used now. The original Dynamo paper mentioned consistent hashing [I read half the paper] ... Precisely => 1. How is it decided which key goes to which partition ? 2. How is it decided which partition goes to which node[physical server] ? Consistent hashing ... works in a bit different way ... all of the people watching this video knows how . For example in normal consistent hashing I guess it is hard to keep a limit on partition size ... I have read some part of the original consistent hashing paper ... in my quest to understand that paper ... somehow I reached your video .. and I thank myself for that.

Well presented and explained well. The best part when Matthias use pointer to exactly mention what part in presentation is under discussion. Thanks 👏

❤