This is urgently needed as we are patching up issues arising from the current state management of shopping baskets....
Ideally we need a basket entity that can persist across client timeouts and reloads - options are local storage, redis cache or mongo... On discussion with Robert we felt using mongo was the preferable route as super performance is not a requirement and we are already using it across the application etc.
create a new basket model with a time to live index on the updated at property (or maybe just the created at ??)...
associate 1:1 on a shopper user id
handle shopping limits here??
reference basket status when deciding how to process bulk items
This is urgently needed as we are patching up issues arising from the current state management of shopping baskets....
Ideally we need a basket entity that can persist across client timeouts and reloads - options are local storage, redis cache or mongo... On discussion with Robert we felt using mongo was the preferable route as super performance is not a requirement and we are already using it across the application etc.