What is the best way to implement a database and work with it for a "basket of goods" on Eloquent Laravel?

Question

Laravel

Hello, I need to do something like a "cart of goods". Please help with advice. There are tables:

users
    id - integer
    email - string

profile
    id - integer
    user_id - integer (внешний ключ к users) 
    name - string 

products
    id - integer
    description - string

korzina
    id - integer
    kolichestvo - integer
    products_id - integer (внешний ключ к products) 
    user_id - integer (внешний ключ к users)

1. Did I make the structure correctly? Or maybe it's better to make a foreign key from the basket to the profile? Or what can you advise on the structure?
2. I need to manage this basket from the profile view (the products will be displayed there) - i.e. a single checkbox on each product and a quantity field - should I make a separate controller for the cart, or is it better to do it in the profile controller?
3. Whether there are somewhere ready simple decisions of the similar? Or how is it even possible to google it to find some guides or something like that?
4. Any of your comments and advice :)
Thank you.

Answer 1

How is a profile different from a user?
Should the cart be linked to a user or a profile?
Can one person have several baskets and the functionality of switching between them?
There is a hypothesis that "translation" is a better fit than "transliteration". Visually cart is better than korzina.
Depending on the answers above, there may be nuances, but the main ideas are:
- The cart is a basic entity. If the connection with the owner is 1-1, then the key can be duplicated. It is not bad to store general information in it - the total amount, weight
- Products are tied to the basket in a separate table, or inside the json field / serialization for reliability. json is my favorite.
- It's nice to store timestamps near the basket
- I would store baskets not in the same mysql database. Either a cache or another DB (like mongoDb), but I'm not sure if this advice is relevant "for a beginner".
- there is a theory that the basket is an order in the "not completed" state. If you follow it, then you should look at it from the point of view of the corresponding architecture. The ideas above do not take this into account.

Answer 2

A table is not needed at all for the basket, unless it is necessary, for example, to spam it later with the letter "you chose something, but did not make an order."
A session or, in extreme cases, a cookie is quite enough, especially for some primitive implementation without a "full-fledged" store.

Answer 3

I propose another option, here you have a korzina table and a products_id cell, so you are tormented with this, it was easier to serialize the basket when ordering so that you can work more conveniently later. Yes, it may not be entirely clear, but believe me, it's worth it, if you write something, I'll explain or even show the source code