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

Implement Delegated Storage #604

Open
19 of 22 tasks
pkosiec opened this issue Jan 10, 2022 · 0 comments
Open
19 of 22 tasks

Implement Delegated Storage #604

pkosiec opened this issue Jan 10, 2022 · 0 comments
Labels
area/hub Relates to Hub enhancement New feature or request needs-triage Relates to issues that should be refined

Comments

@pkosiec
Copy link
Member

pkosiec commented Jan 10, 2022

Description

Implement Delegated Storage according to the accepted proposal.

NEW

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)

AC

  • in each sub-task check for 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:

  • It’s a resource intensive
  • Better local dev/test experience with lightweight alternative (not in Java)
  • Option to create interactive tutorials, e.g. using katacoda: https://www.katacoda.com/. In that way, you can try our solution e2e without installing anything on your local machine. Currently, neo4j takes too much CPU and memory.
  • GPL3 license will scare people away
  • Not fully optimized for our use case (we got it working but it’s not ideal)

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.

@pkosiec pkosiec transferred this issue from another repository Jan 20, 2022
@pkosiec 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
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
Projects
None yet
Development

No branches or pull requests

1 participant