← AI Product Manager

Backend Concepts Every PM Should Know (No Code Required)

Video 1 of 1 · 4:06

Transcript

Auto generated by YouTube. Click any timestamp to jump to that moment.

Show
  1. 0:03you need to understand how back-end
  2. 0:05behave.
  3. 0:07that understanding is what makes
  4. 0:10Claude code prompts actually work
  5. 0:13production, not just in demos.
  6. 0:16are four concepts that will change
  7. 0:19you build and how you talk about
  8. 0:23a coffee shop.
  9. 0:25synchronous barista takes your order,
  10. 0:27your coffee, hands it to you, then
  11. 0:30the next person's order. Everyone
  12. 0:32An async barista takes your
  13. 0:35gives you a number, and starts
  14. 0:37the next person while your
  15. 0:38is being made.
  16. 0:40your app, when a user clicks generate
  17. 0:43you call Open AI, that takes 3 to 5
  18. 0:46If you do that synchronously,
  19. 0:48whole UI freezes. Nothing responds.
  20. 0:52fix is simple. Make the call async.
  21. 0:55a loading state immediately. Let
  22. 0:57user keep interacting. Update the
  23. 1:00when the response arrives.
  24. 1:02users open your app at the same
  25. 1:05Both click claim this spot on
  26. 1:08last available slot. Your back-end
  27. 1:10the database, sees one spot left,
  28. 1:13confirms both. But there was only
  29. 1:15spot. Now you have a double booking.
  30. 1:19is a race condition. You don't need
  31. 1:22write the fix, but you need to spot
  32. 1:24pattern in your specs. Anytime a
  33. 1:27action reads a value and then
  34. 1:29it, ask your engineer one
  35. 1:31What happens if two users do
  36. 1:34at the same time? The fix is an
  37. 1:37transaction. The read and the
  38. 1:40happen as one indivisible
  39. 1:44you want to learn how to do this
  40. 1:46I run free live sessions every
  41. 1:49at noon Eastern.
  42. 1:52the QR code on screen to join.
  43. 1:55love to see you there.
  44. 1:58user submits a form.
  45. 2:00internet cuts out for half a
  46. 2:02Did the request go through? They
  47. 2:05know, so they click again.
  48. 2:08your API is not item potent, you now
  49. 2:11two records for the same
  50. 2:14it is item potent, the second request
  51. 2:17the same result without creating
  52. 2:19duplicate.
  53. 2:21standard fix is an item potency key.
  54. 2:24unique ID generated on the front end,
  55. 2:27with every request.
  56. 2:29back-end checks if it already
  57. 2:31that key.
  58. 2:32yes, it returns the cached result.
  59. 2:35uses this pattern for every
  60. 2:37call.
  61. 2:39app calls Open AI and the API is
  62. 2:43does the user see? If you haven't
  63. 2:46about this, they see a blank
  64. 2:48or a raw error code. That is your
  65. 2:51not the engineers.
  66. 2:53feature you spec needs three
  67. 2:56The happy path, where everything
  68. 2:58The loading state, where we're
  69. 3:01And the error state, where
  70. 3:03failed. If you define all
  71. 3:05engineers build all three.
  72. 3:08the call up to three times. If it
  73. 3:12fails, show a friendly message and
  74. 3:14the rest of the page working. Never
  75. 3:17one dependency take down the whole
  76. 3:21time you're in Claude code, try
  77. 3:24one of these terms in your prompt.
  78. 3:26it to handle something
  79. 3:29make an endpoint item potent. Or add
  80. 3:33degradation.
  81. 3:35notice the output gets
  82. 3:36better when you speak the
  83. 3:38language as the system.
  84. 3:41the full picture. If you want to
  85. 3:43deeper, join my free live session
  86. 3:46Friday at noon Eastern on Maven. I
  87. 3:49through this hands-on, answer
  88. 3:51and show you how to build it
  89. 3:53Scan the QR code to join.

Want the next one in your inbox?

Join 1,000+ Product Managers getting one deep dive every Friday.