The latest articles on Forem by ERICK MIRANDA G (@erick_mirandag_aea76fba9). https://forem.com/erick_mirandag_aea76fba9 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3858547%2F05e19223-663b-40d6-a8c0-deb01ac13059.png https://forem.com/erick_mirandag_aea76fba9 en ERICK MIRANDA G Fri, 03 Apr 2026 02:06:24 +0000 https://forem.com/erick_mirandag_aea76fba9/where-should-i-handle-inserting-data-into-multiple-related-tables-frontend-or-backend-2cp5 https://forem.com/erick_mirandag_aea76fba9/where-should-i-handle-inserting-data-into-multiple-related-tables-frontend-or-backend-2cp5 <p>My current structure is:</p> <p>Table</p> <ul> <li>Order</li> <li>Product </li> </ul> <p>In the UI, the user creates a new order and dynamically adds multiple products to it within the same interface. When the user finishes, there is only one submit button that sends all the information.</p> <p>For example, should the frontend send multiple requests (one for the order and others for products), or should it send one request containing everything and let the backend manage database operations?</p> <p>Additionally, the products are not reused. Each product is unique and is created at the moment the user submits the order. In other words, products do not exist beforehand in a catalog; they are generated dynamically as part of the order creation process.</p> architecture backend database discuss