Do you think you making PowerPoints of the concepts that you covered in this entire series helped you with your long term understanding of the fundamentals. Essentially can creating a PowerPoint on a topic be a high yield method of learning.
Hey Jordan! First, Your videos are really helping me out for interview prep. I have a question tho about HBase. How would the HBase schema look like for storing documents? What is going to be the row key, sort key and what about the columns?
hello @@jordanhasnolife5163 , I want to clarify the db schema for an event of an insertion in OT. Let's say our server gets an insert request for a document at index "i". In that case I believe this request does not only effect documentIndex at "i" but we also need to propagate this change to rest of the indexes by incrementing them by 1 in our db. Don't you think this has negative impact on db writes?
So, based on the schema given below, what is documentIndex? I understand documentId is unique for entire document. Is docIndex similar to pageNumber? So, each docId has multiple docIndexes? Does each character become a separate Row in the DB? Isn't it a lot? Can't we store entire line as a Row?
HBase is column oriented storage which is nice if you want to get lower latency just getting the characters in the doc as opposed to a bunch of metadata which will probably be in the db
Yes but deletions are tricky in the sense that they require FIFO broadcast - you can't delete a character unless it already exists, so you need to make sure that at least from a single client, all of the operations are being broadcast in the correct order
