Demo scenario: Shopping Cart Component

[dhmlau]

Description / Steps to reproduce / Feature proposal

As part of the e-commerce store demo scenario in #1476, this task is to create the Shopping Cart component. Shopping cart data will be stored in a distributed in-memory cache, e.g. Redis.

Questions:

• Are we going to use Redis?
  • Yes
• Is it going to be another LB app? If so, then I believe it will be blocked by [Epic] KeyValue repository #1447 (KeyValue Repository task)
  • Controller within the same application that uses the KVRepository.

Acceptance Criteria

• Controller + KV Repository for Redis Database
• Mockup / Dockerize a Redis Instance for use with this
• Simple Model: Cart (id) containing multiple Products (ids + quantity)
• A REST API controller either full CRUD or at least the APIs that make sense for this component

[bajtos]

Yes, this is blocked by #1447, I am relabelling this story as p2.

[bajtos]

In progress by @raymondfeng - see loopbackio/loopback4-example-shopping#4

[bajtos]

The acceptance criteria don't not describe any Controller (REST API), is that intentional?

IMO, a shopping cart component is not complete without a REST API to access the data.

[virkt25]

Controller + KV Repository for Redis Database

When I wrote the acceptance criteria it was with the intention that there will be a full CRUD controller for this component. -- This is also meant to be reflected in the estimate this task was given of an 8.

My apologies for not being more specific -- but a full CRUD controller (or at least the APIs that make sense for this Model / Controller).