Dumb question. All this logic (coordinating the transaction and keeping the commit log) has to be implemented in the API calling the DBs or is it something that is already solved and implemented in, for example, an ORM or DB Libraries that would be consumed by the API that calls the DBs and then one would need to configure the DB to enable such functionality?
It actually depends on the database. If all the nodes are one piece of software, there may be an existing solution internally. If this is a "heterogenous" transaction you may have to write the logic yourself.
Hey bro, I passed 2 onsites thanks to your videos. But I still have no offer as the companies I interviewed at said they have no headcount until later this year It’s super frustrating to go thru 10+ rounds of interviews and have nothing to show for it 😞
Hey man! First off, really proud to hear that, congrats and keep killing it! I'm sorry they don't have headcount right now, but even just the fact that you're passing should show you that you're on the right path and to keep persevering - remember when only grow stronger from our failures!
You said at 7:47 "we can improve locality with NoSql or Document store database that are going to generally allow to avoid these cross-partition writes" My question is how noSql or Document store databases enable that?
I really should have just said denormalization. But the gist is if you can store all data on the same node for a given record when writing, you don't have to hit multiple nodes and do a two phase commit.
Are you planning on covering 3 phase commit and saga next ? For 2 phase commit I think it's important to mention issues that arise due to coordinator or participating node failure in middle of transaction which makes 3 phase commit better option. As always appreciate all your videos and it's been super helpful for my prep. Thank you!
Truthfully haven't ever particularly looked into them much since I assumed it was a bit too niche for an interview, but maybe I will within the next few days and if it's relevant then I'll cover them! Thanks for the suggestion
recruiters do 2 phase commit with me. In first commit , they reach out for interviews , and in second commit they ghost me
This is quality
You have the best videos on system design i found on RUclips that really dive deeper on the topics. Thank you for this!
You have really good detailed videos on system design. It is making my life easier to learn all these at one place :)
What a dialogue to start the video man.. Crazyy
Dumb question. All this logic (coordinating the transaction and keeping the commit log) has to be implemented in the API calling the DBs or is it something that is already solved and implemented in, for example, an ORM or DB Libraries that would be consumed by the API that calls the DBs and then one would need to configure the DB to enable such functionality?
It actually depends on the database. If all the nodes are one piece of software, there may be an existing solution internally. If this is a "heterogenous" transaction you may have to write the logic yourself.
Hey bro, I passed 2 onsites thanks to your videos.
But I still have no offer as the companies I interviewed at said they have no headcount until later this year
It’s super frustrating to go thru 10+ rounds of interviews and have nothing to show for it 😞
Hey man! First off, really proud to hear that, congrats and keep killing it! I'm sorry they don't have headcount right now, but even just the fact that you're passing should show you that you're on the right path and to keep persevering - remember when only grow stronger from our failures!
I hope Jordan has a life, thanks a lot. :)
You said at 7:47 "we can improve locality with NoSql or Document store database that are going to generally allow to avoid these cross-partition writes" My question is how noSql or Document store databases enable that?
I really should have just said denormalization. But the gist is if you can store all data on the same node for a given record when writing, you don't have to hit multiple nodes and do a two phase commit.
Are you planning on covering 3 phase commit and saga next ? For 2 phase commit I think it's important to mention issues that arise due to coordinator or participating node failure in middle of transaction which makes 3 phase commit better option.
As always appreciate all your videos and it's been super helpful for my prep. Thank you!
Truthfully haven't ever particularly looked into them much since I assumed it was a bit too niche for an interview, but maybe I will within the next few days and if it's relevant then I'll cover them! Thanks for the suggestion
I have looked into them and deemed them a bit too niche, but check the description :)
HODL and trust the process. Bitcoin is here to stay
;dfkjh;alsdfhd;asf
Hi Jordan can i get your mail id??
Not sure what you mean mail ID but feel free to contact me on LinkedIn