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

[EPIC] Create Gateway Service #18

Closed
nnnnat opened this issue Jan 31, 2020 · 0 comments · Fixed by #20
Closed

[EPIC] Create Gateway Service #18

nnnnat opened this issue Jan 31, 2020 · 0 comments · Fixed by #20
Assignees

Comments

@nnnnat
Copy link
Contributor

nnnnat commented Jan 31, 2020

Create Gateway Service

In this EPIC we'll create the actual Federated Gateway service. Our Gateway will need to use Apollo Gateway and conform to the Apollo Federation spec.

User Stories

  • As a developer I should be able to add services to the Gateway via an .env variable.
  • As a developer I should be able to query through the Gateway endpoint and view federated data from across the reaction node and pricing engine services.
  • As a developer I need to enforce system level permissions in the Gateway: [EPIC] IAM Integration #4

Acceptance Criteria

  • Gateway service available that includes Reaction 3.0 API and the Pricing Engine API.
  • We can query products from the Gateway and see Pricing Engine data included.
  • Verify system level access control is working.

Consideration

The Gateway services it's self is a pretty small application and most examples show it being used directly with Apollo Server. I think it's worth the effort to create the Gateway using a more common node.js server (express, hapi, koa, etc) and provide Apollo via a middle-ware, this will give us a little more granular control of the server it's self and removes some of the apollo magic.

@nnnnat nnnnat added the epic For issues that exist only to track progress on a list of other issues in one place label Jan 31, 2020
@nnnnat nnnnat added this to the Federated Gateway - Phase 1 milestone Jan 31, 2020
@kkuzemka kkuzemka removed the epic For issues that exist only to track progress on a list of other issues in one place label Feb 7, 2020
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.

4 participants