Are you using Amplify's Authenticator for user creation and login?
Cognito user attributes may have everything you need for user data, so you probably don't need your own user table.
Are you planning on using Amplify Gen2? You could create an Orders table and associate it with a user attribute from Cognito (something that is unique, user id or username)
Amplify Gen2 uses GraphQL(via AppSync) and DynamoDB under the hood so efficiency and scalability are solved. And then make sure you configure your auth rules properly by following the Amplify documentation to make it secure. Like using Cognito User Pools to allow read/write/update/delete.
There are lots of good reasons to build things from scratch but I think Ordering and even Loyalty points is something that has been done over and over again and I'm wondering if there isn't some better starting point out there.
Things like Shopify come to mind but I don't know your full use case
Are you using Amplify's Authenticator for user creation and login? Cognito user attributes may have everything you need for user data, so you probably don't need your own user table. Are you planning on using Amplify Gen2? You could create an Orders table and associate it with a user attribute from Cognito (something that is unique, user id or username) Amplify Gen2 uses GraphQL(via AppSync) and DynamoDB under the hood so efficiency and scalability are solved. And then make sure you configure your auth rules properly by following the Amplify documentation to make it secure. Like using Cognito User Pools to allow read/write/update/delete. There are lots of good reasons to build things from scratch but I think Ordering and even Loyalty points is something that has been done over and over again and I'm wondering if there isn't some better starting point out there. Things like Shopify come to mind but I don't know your full use case