Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Demo scenario: Product Recommendation component #1482

Closed
2 tasks done
dhmlau opened this issue Jun 26, 2018 · 2 comments · Fixed by loopbackio/loopback4-example-shopping#20
Closed
2 tasks done

Demo scenario: Product Recommendation component #1482

dhmlau opened this issue Jun 26, 2018 · 2 comments · Fixed by loopbackio/loopback4-example-shopping#20
Assignees

Comments

@dhmlau
Copy link
Member

dhmlau commented Jun 26, 2018

Description / Steps to reproduce / Feature proposal

As part of the e-commerce store demo scenario in #1476, this task is to create the Product Recommendation component. Information will be fetched from a SOAP/REST service.

Questions:

  • Do we want SOAP service instead of REST service?
    • Use REST for now, SOAP can be a different branch / service at a later date. The main concept to show off is the Service Proxy integration / Usage.

Acceptance Criteria

  • Controller using service proxy to talk to Product Recommendation REST API
  • Mockup of Product Recommendation Service (Express / LoopBack App / Serverless Function).
@b-admike
Copy link
Contributor

b-admike commented Aug 9, 2018

I don't have a strong opinion on whether the operation(s) depend on SOAP service(s) or REST API, but if the other components are using REST, then we might want to use SOAP for diversity.

@raymondfeng
Copy link
Contributor

Let's start with REST and add SOAP if necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants