-
Notifications
You must be signed in to change notification settings - Fork 19
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
Implement Delegated Storage #604
Labels
area/hub
Relates to Hub
enhancement
New feature or request
needs-triage
Relates to issues that should be refined
Comments
Closed
pkosiec
added
area/hub
Relates to Hub
enhancement
New feature or request
needs-triage
Relates to issues that should be refined
labels
Jan 20, 2022
This was referenced Feb 15, 2022
8 tasks
5 tasks
This was referenced Mar 9, 2022
This was referenced Mar 15, 2022
This was referenced Mar 25, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/hub
Relates to Hub
enhancement
New feature or request
needs-triage
Relates to issues that should be refined
Description
Implement Delegated Storage according to the accepted proposal.
- Make sure Populator supports it
- Support it in GraphQL API
- Find Types based on prefix of parent nodes (consider refactoring Cypher query to TypeScript)
Rewrite Local Hub to Go #605 [13MD]droppedbackend.id
(Policy, Workflow, GraphQL) #624capact-outputTypeInstances
syntaxNEW
Total SP:
- Minimal scope: 46 SP + padding 15% = 53 SP (~ 7 weeks)
- Target architecture: 74 SP + padding 15% = 85 SP
Additional subtasks (not required for minimal scope)
taking into account the Potential feature evolution which may impact implementation
AC
TODO(https://github.com/capactio/capact/issues/604)
and if applicable, resolve it.Reason
We want to be able to consume and save data into external backends. In that way we can integrate easily with 3rd party applications/services/platforms. We will solve also the security issues as one of the delegated storage can be e.g., Vault. Another benefit is to get rid of Neo4j and make Capact lightweight.
Why it's worth to replace the Neo4j:
SCOPE: Only the Local Hub. Probably in the next phases this can be integrated/reused to other parts of our system, e.g., Public Hub.
The text was updated successfully, but these errors were encountered: