![]() ![]() Interviewer: Due to extremely high security and compliance requirements, we do not store card numbers directly in our system. ![]() Interviewer : No, we use third-party payment processors, such as Stripe, Braintree, Square, etc.Ĭandidate: Do we store credit card data in our system? However, in this interview, we can use credit card payment as an example.Ĭandidate : Do we handle credit card payment processing ourselves? Interviewer : The payment system should support all of these options in real life. When a customer places an order on, the payment system handles everything related to money movement.Ĭandidate : What payment options are supported? Credit cards, PayPal, bank cards, etc? Interviewer : Assume you are building a payment backend for an e-commerce application like. These are some questions you can ask the interviewer:Ĭandidate : What kind of payment system are we building? It is very important to determine the exact requirements at the beginning of the interview. Others may think it’s a backend system that handles payments such as PayPal or Stripe. Some may think it’s a digital wallet like Apple Pay or Google Pay. If you find this chapter useful, get System Design Interview: Volume 2 :Īs usual, I aim to stay independent with my recommendations: I have no financial association with this book, nor have I been paid to mention it, and there are no affiliate links in this email.Ī payment system can mean very different things to different people. This issue covers the following topics - straight from the book: I had to learn most of what Alex covers the hard way: through working on a payments system, asking around, and trial-and-error. However, this summary does an excellent job, of balancing conciseness and going deep enough. The reality is that a book can’t cover all real-life scenarios when building a payments system. I also reviewed the Payments chapter as Alex was writing it. I chose the Payments System chapter, as I worked on payments systems for years at Uber, and building payments systems requires understanding some terms like payment service, payment executor, PSP (Payment Service Provider), ledger or wallet. Propose high-level design and get buy-in.Īlex has kindly agreed to share a full chapter from the book with newsletter readers. Understand the problem and establish the design scope. The book follows a four-step process for each chapter: The two of them wrote the book for 1.5 years and got feedback and reviews from experienced engineers at Amazon, Google, eBay, Instacart, Tencent, Twitter, Microsoft, Airbnb, TikTok and others. For this second edition, he pulled in co-author Sahn Lam who previously worked at Discord, Zynga and NetApp. Alex worked at Zynga, Apple and Twitter, before leaving his full-time job behind to go all-in writing the first edition of the book. I connected with Alex after reading and reviewing the original Systems Design Interview book, and he had just started working on the second edition. I had the opportunity to read the book before it was released and I’m impressed by both the depth, and the attention to detail. These include building a proximity service, a nearby friends feature, Google Maps, distributed messaging queue, metrics monitoring and alerting, a hotel reservation system, real-time gaming leaderboard, digital wallet, stock exchange and more. The book contains 13 original and in-depth systems design challenges not covered anywhere else. As of writing, the book is the best-selling computer science book on Amazon in the US, and for good reason. My friend Alex Xu released Systems Design Interview: An Insider’s Guide: Volume 2 two days ago. ![]() In every issue, I cover challenges at big tech and high-growth startups through the lens of engineering managers and senior engineers. □ Hi, this is Gergely with a bonus issue of the Pragmatic Engineer Newsletter.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |