Sir, again! This is pure gold, normally I had a tremendous nervous about getting System Design interview, then after this channel, I aced two different interviews and getting two offers. Thank you for this!
You guys are doing an incredible job. The information is so helpful, and I really appreciate how you start simple and gradually build up to more complex concepts
Amazing walk-through. I love all the content you guys produce. I would have loved to see a brief section explaining how geospatial search works in elasticsearch
You're creating great content! Thanks a lot. It would be even better you could put some other study materials in the end in case we may want to dig deeper into some aspects of the topic.
@@hello_interview I use a combination of bucket and metric aggregations. eg. Terms aggregations followed by a metric or even for time series, date histogram>term>metric I'd be interested in knowing how the memory loading works at each level of aggregation. In my case, the metric sits at the root level while date histogram and terms fields are nested
Quite informative. In the last slide with the callflow diagram, how does the Coordinating Node know on which shard the data is found? I am guessing that the Ingest Node communicates with it and provides this information to it, right? The callflow diagram did not indicate this.
Was waiting for this. :) As always, useful and awesome. One doubt that I had is that the Elasticsearch and Cassandra deep dives are not showing on the website for me, in India. Is it not live yet? Or some other issue?
Thanks for sharing the details. It looks like the segments and deletion looks similar to LSM. Does Elastic search also use memtable and LSM ? I will anyway dig a bit more on the Elastic Search documentation.
Thanks for the amazing content and efforts you guys putting into each video, I really like the clean ui of the software you are writing with can you please point me out which software is this? I did my research and found none similar :(
10:50 - Sending a GET request with a body is unspecified behavior in the RFC 7231 (HTTP/1.1 Spec): "A payload within a GET request message has no defined semantics", so, from a purely RESTful design POV, the API seems hokey. However, I don't know what else they could've done, given the limitation on the length of the URL. Message body also has a limit, but it's way more than the URL length limit. If I was designing such an API in a SD interview, I'd call this out to the interviewer, and explain the reason for choosing a non-standard implementation.
the informations in your videos are invaluable but why are they always blurry; i find it very difficult to see the texts in your video; Can you improve of that please.
watch this repeatedly to grasp the concepts and details of elasticsearch. Thank you so much!
Sir, again! This is pure gold, normally I had a tremendous nervous about getting System Design interview, then after this channel, I aced two different interviews and getting two offers.
Thank you for this!
You rocked it! Major congrats on your success, don’t give us too much credit :)
@@hello_interview hahahahah you are really humble, but following this framework, also the interviewers loved the approach, this is thanks to you guys.
Thank you, no fluff, channel is pure discussing engineering concepts with tradeoffs :)
You guys are doing an incredible job. The information is so helpful, and I really appreciate how you start simple and gradually build up to more complex concepts
Amazing walk-through. I love all the content you guys produce. I would have loved to see a brief section explaining how geospatial search works in elasticsearch
Excellent explanation! I now have a full understanding of many aspects of Elasticsearch. Thanks for putting this together!
I bought the guided system design course. Amazing content sir!
Amazing! Let us know how you like it, we’re launching new features every couple days with the guided practice.
So simple and powerful explanation of Elasticsearch, thank you!
Excellent tutorial :) Fluid search knowledge. I am learning about ElasticSearch.
I was just about to learn about elastic search and you've posted this. Thank you so much!
Amazing. Let us know what we're missing!
You're creating great content! Thanks a lot. It would be even better you could put some other study materials in the end in case we may want to dig deeper into some aspects of the topic.
This was amazing. Thank you Stefan!
Great video. Personally, a bulk of my elasticsearch use case pertains to analytics with aggregations. It would awesome to have a deep dive into that!
What do you use it for?
@@hello_interview I use a combination of bucket and metric aggregations. eg. Terms aggregations followed by a metric or even for time series, date histogram>term>metric
I'd be interested in knowing how the memory loading works at each level of aggregation. In my case, the metric sits at the root level while date histogram and terms fields are nested
Amazing! it's finally here.
Quite informative. In the last slide with the callflow diagram, how does the Coordinating Node know on which shard the data is found? I am guessing that the Ingest Node communicates with it and provides this information to it, right? The callflow diagram did not indicate this.
🔥🔥 great for learning or reviewing concepts. Thank you
do I need this for a grad/junior role?
Interesting. Slowly things became clearer and more relevant. Please do same on MongoDB
Was waiting for this. :) As always, useful and awesome. One doubt that I had is that the Elasticsearch and Cassandra deep dives are not showing on the website for me, in India. Is it not live yet? Or some other issue?
Should be fixed in 30 minutes with the next deploy!
Simply top notch!
Drop everything you doing, and watch the new episode in Deep Dives series🎬📽🍿
Very concise and informative!
Thanks for sharing the details. It looks like the segments and deletion looks similar to LSM. Does Elastic search also use memtable and LSM ? I will anyway dig a bit more on the Elastic Search documentation.
as far as I know it's almost similar but Elasticsearch does not use the in-memory buffer(mmetable) for the query
Thanks for the amazing content and efforts you guys putting into each video, I really like the clean ui of the software you are writing with can you please point me out which software is this? I did my research and found none similar :(
Excalidraw
@@hello_interview Thanks dear, highly appreciate it
@@karrarkazuya8898 here for this. :)
Thank you
Why no written article on website sensei ?
Link in the description!
10:50 - Sending a GET request with a body is unspecified behavior in the RFC 7231 (HTTP/1.1 Spec): "A payload within a GET request message has no defined semantics", so, from a purely RESTful design POV, the API seems hokey. However, I don't know what else they could've done, given the limitation on the length of the URL. Message body also has a limit, but it's way more than the URL length limit.
If I was designing such an API in a SD interview, I'd call this out to the interviewer, and explain the reason for choosing a non-standard implementation.
Plz make course for Docker and kubernetes as well if possible
kubernetes +1
Video request: design guided practice feature for an interview prep service.
😂😂😂
So well explained
the informations in your videos are invaluable but why are they always blurry; i find it very difficult to see the texts in your video; Can you improve of that please.
Thank you!
Table of contents not updated with topic but good content :)
Should be fixed now!