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

Change to using a graph database #85

Open

MarkNSweep opened this issue Oct 3, 2016 · 0 comments

Labels

Epic

Milestone

Member

MarkNSweep commented Oct 3, 2016 •

edited by ebullient

Loading

The current NoSQL implementation of Map has some drawbacks:

Empty rooms must be pre-allocated to make it easier to place rooms...
We collect tombstones (couchdb/Cloudant do not ever really delete rooms)
Very difficult to support the notion of suites

MarkNSweep added this to the OSCon-London-2016 milestone

ebullient modified the milestones: Devoxx-US-2017, OSCon-London-2016

ebullient added the Epic label

ebullient modified the milestones: JavaOne-2017, Devoxx-US-2017

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