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.

Sign up for GitHub

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

Jump to bottom

Write an article about why we choose Grakn over Neo4j #7

Closed
manonviallet opened this issue Apr 17, 2019 · 1 comment
Closed

Write an article about why we choose Grakn over Neo4j #7

manonviallet opened this issue Apr 17, 2019 · 1 comment
Assignees
@SamuelHassine
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone
Release 1.1.1

Comments

@manonviallet
Copy link
Contributor

manonviallet commented Apr 17, 2019 •
edited by SamuelHassine
Loading

Problem to Solve

To explain technical choices behind OpenCTI, we have to write an article about why we choose Grakn as the main database backend.

Current Workaround

None.

Proposed Solution

Clean the Luatix blog and write the article.

Additional Information

None.
@SamuelHassine SamuelHassine added this to the 1.0-beta milestone Apr 20, 2019
@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label Apr 20, 2019
@SamuelHassine SamuelHassine self-assigned this Apr 20, 2019
@SamuelHassine SamuelHassine modified the milestones: v1.0.0-beta, v1.0.0 Jun 17, 2019
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jul 29, 2019
@SamuelHassine SamuelHassine added this to the Release 1.1.1 milestone Jul 29, 2019
@SamuelHassine
Copy link
Member

A blog post that explains why we choose Grakn has been published: https://www.luatix.org/en/2019/07/22/open-sourcing-the-opencti-platform/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SamuelHassine SamuelHassine

Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Milestone
Release 1.1.1
Development

No branches or pull requests
2 participants
@SamuelHassine @manonviallet