Fantastic videos but I found it less interesting as in the whole video you were holding a pen and blank white board at the back, I think you should draw some sort of design diagrams on the board or use some online tools to illustrate the design.
I believe it's better to have some diagrams or pictures to represent the design instead of just oral description because it's really difficult to understand these kind of terminology
Thanks for the comment. This video was a bit different from my previous videos as I wanted to evaluate a new format for the videos. Btw, there are video/diagram representations in between if you haven't check.
Thanks for your sharing. I'm curious about the design. How did you learn to build Uber or any payment system like this video? Not much info available online. So, how do you teach yourself about the field? Is there any way to find any sample code online or from any other resources? Thanks a lot.
How are do you plan to design a horizontal scalable system that is both highly Available and strongly consistent at the same time.? CAP theorem choose 2 out of three
Thanks for the question. This has asked multiple times in this channel and I have answered them before as well. I think people have wrong understanding of CAP theorem and its applicability. Now the question arises that how a service is available and consistent at the same. It boils down to the fact that no service is 100% available. Question arises whether we are targeting five 9s or four 9s of availability and again it also boils down to whether we are talking about availability of the whole service or some part of it. The service itself can be highly available (as a whole with 5 9's or 6 9's of availability) and at the same time fulfill consistency requirement as a whole (keyword is "as a whole") however the individual partitions (in the datastore) may have to prefer either availability or consistency. Now it is totally possible that one partition could be down due to network partition but it won't affect the functionality and availability of other partitions, thus overall service still considered as highly available. I hope this clarifies.
@@ThinkSoftware Appreciate the response , it does clarify. I have another question In the scenario above, I am assuming that these partitions are on different nodes as you say "Now it is totally possible that one partition could be down due to network partition but it won't affect the functionality and availability of other partitions". So would that mean you would be choosing a NoSQL data store. From what i understand it is quite challenging to shard a RDBMS databases. For example writing Join queries that may need to span multiple nodes can be a very expensive operation also Group by etc.
I really appreciate the effort. However, the very basics of system design is missing. One of them is the HLD (High level design). Second is some UML diagrams. That will make the design complete. That would deliver the best than simply delivering the speech.
Thank you for your video, quick question. Why the issuer bank first freeze the money, and do the real transfer money at the end of the day? Can they transfer the money from the issuer bank to acquirer bank during the runtime per transaction instead of the batch job? what is the trade-off here?
This is due to distributed nature of the system. The fault can occur at any point in the return path causing the transaction to be lost or double charge the customer. I think I have covered this in the video if you watch it complete. The more details are in the course.
We created a subscription product directly from Stripe. It's a 6-month payment plan. Upon reaching the 6th-month payment, it had deductions. Stripe said that it was due to proration. They said that we should have canceled the subscription before it reached the 6th-month payment to avoid the prorated amount. What does that mean? Does it mean that if we create a 6 monthly subscription, we will need to stop it on the 5th month? Does that make sense? I really need to be enlightened about this. I want to utilize Stripe well but I also need to be clear on how things should work. I would really appreciate your help. Thank you so much in advance.
Specific to the service that would be driving transactions, the service should be consistent and highly available. As per CAP, thus the system does not become partition tolerant. Hence the system relies on transactional DBs and uses hot/hot backup
Very bad explanation and misleading title. If lots of people telling you the same then instead of fighting with them in the comment please understand why multiple people saying the same things. Where is system design ?
I appreciate your efforts in making videos. But these videos looks like click baits, discussing ONLY requirements, no system was designed and at the end trying to sell your courses. I think this doesn't look like a sustainable way to run your youtube channel.
This is the worst system design interview anyone following this system design approach will fail for sure, this just speaks of stripe service not even close to system design
I felt its more of functional. No system design. How is the design how to scale is what we want to see in system design. Please cover those. I see lot of people commenting its not system design but your replies are introduction. I wasted 1 hour trusting will get an overall system design. Request you to remove system design from title.
Please let me know if you find this video useful. Also please don't forget to like and comment and subscribe to the channel. Thanks :)
Fantastic videos but I found it less interesting as in the whole video you were holding a pen and blank white board at the back, I think you should draw some sort of design diagrams on the board or use some online tools to illustrate the design.
Is there any coupon code for "The Distributed System Design Interviews Bible" course?
Right now a black friday discount going on which will expire on 30th Nov. Check www.thinksoftwarelearning.com
I think you should change summary of this video as requirement gathering for payment gateway systems not the design of systems.
I believe it's better to have some diagrams or pictures to represent the design instead of just oral description because it's really difficult to understand these kind of terminology
Thanks for the comment. This video was a bit different from my previous videos as I wanted to evaluate a new format for the videos. Btw, there are video/diagram representations in between if you haven't check.
It is because more details are included in his online course 😐
Is it through that stripe renders the payment form in the merchant's website such that merchant do not require to be PCI DSS compliant
Thanks for your sharing. I'm curious about the design. How did you learn to build Uber or any payment system like this video? Not much info available online. So, how do you teach yourself about the field? Is there any way to find any sample code online or from any other resources? Thanks a lot.
Thanks for the comment 🙂. I am designing these services by myself based on my 18+ years of industry experience
How are do you plan to design a horizontal scalable system that is both highly Available and strongly consistent at the same time.? CAP theorem choose 2 out of three
Thanks for the question. This has asked multiple times in this channel and I have answered them before as well. I think people have wrong understanding of CAP theorem and its applicability. Now the question arises that how a service is available and consistent at the same. It boils down to the fact that no service is 100% available. Question arises whether we are targeting five 9s or four 9s of availability and again it also boils down to whether we are talking about availability of the whole service or some part of it. The service itself can be highly available (as a whole with 5 9's or 6 9's of availability) and at the same time fulfill consistency requirement as a whole (keyword is "as a whole") however the individual partitions (in the datastore) may have to prefer either availability or consistency. Now it is totally possible that one partition could be down due to network partition but it won't affect the functionality and availability of other partitions, thus overall service still considered as highly available. I hope this clarifies.
@@ThinkSoftware Appreciate the response , it does clarify. I have another question In the scenario above, I am assuming that these partitions are on different nodes as you say "Now it is totally possible that one partition could be down due to network partition but it won't affect the functionality and availability of other partitions". So would that mean you would be choosing a NoSQL data store. From what i understand it is quite challenging to shard a RDBMS databases. For example writing Join queries that may need to span multiple nodes can be a very expensive operation also Group by etc.
You can shard RDBMS but then you should shared-nothing architecture for the partitions so you wont be using joins etc across partitions
I really appreciate the effort. However, the very basics of system design is missing. One of them is the HLD (High level design). Second is some UML diagrams. That will make the design complete. That would deliver the best than simply delivering the speech.
Love this
Thanks ☺️
Thanks for video
Most welcome
Your explanation is more close to product design than system design
Thanks for the comment. Yes this is also the title in the title picture as well
I don't recommend watching this. it's nowhere close to system design video
Thanks for the comment. This is introduction video as the title suggest.
Thank you for your video, quick question. Why the issuer bank first freeze the money, and do the real transfer money at the end of the day? Can they transfer the money from the issuer bank to acquirer bank during the runtime per transaction instead of the batch job? what is the trade-off here?
This is due to distributed nature of the system. The fault can occur at any point in the return path causing the transaction to be lost or double charge the customer. I think I have covered this in the video if you watch it complete. The more details are in the course.
We created a subscription product directly from Stripe. It's a 6-month payment plan. Upon reaching the 6th-month payment, it had deductions. Stripe said that it was due to proration. They said that we should have canceled the subscription before it reached the 6th-month payment to avoid the prorated amount. What does that mean? Does it mean that if we create a 6 monthly subscription, we will need to stop it on the 5th month? Does that make sense? I really need to be enlightened about this. I want to utilize Stripe well but I also need to be clear on how things should work. I would really appreciate your help. Thank you so much in advance.
You should take this question to stripe support. I don't have any association with stripe.🙂
Hello how can I get contact with you Sir?
Much needed
Thanks for the comment
Based on CAP, we can not reach strong consistency and highly available at the same time, isn't it?
Most people don't understand at what level CAP theorem is applicable. This I have discussed in the course.
Specific to the service that would be driving transactions, the service should be consistent and highly available. As per CAP, thus the system does not become partition tolerant. Hence the system relies on transactional DBs and uses hot/hot backup
How can I reach your online course related to payments please?
Through the website mentioned in the description of the video.
misleading, this is not a design video.
Title also suggest that this is introduction and requirement collection. What is misleading here?
Bro I dont think you designed uber
watched. --
feels like an ad for Stripe...
Very bad explanation and misleading title. If lots of people telling you the same then instead of fighting with them in the comment please understand why multiple people saying the same things. Where is system design ?
Where is Design?
In the course.
😂
I appreciate your efforts in making videos. But these videos looks like click baits, discussing ONLY requirements, no system was designed and at the end trying to sell your courses. I think this doesn't look like a sustainable way to run your youtube channel.
This is the worst system design interview anyone following this system design approach will fail for sure, this just speaks of stripe service not even close to system design
This video is an introduction video and discusses the requirements for Stripe product design as the title suggests.
I felt its more of functional. No system design. How is the design how to scale is what we want to see in system design. Please cover those. I see lot of people commenting its not system design but your replies are introduction. I wasted 1 hour trusting will get an overall system design. Request you to remove system design from title.
You misleading highly, change your title . These tricks won’t help you in the long term
Thanks for the comment. What should be the title then if it is not introduction and requirements? I think you misunderstood.
This is all business logic. Who has to provide business logic? This has nothing to do with usual system design interview expectation
What a waste of time, where are the desing diagram?
Beware of using Stripe
any particular reason?