+------------------+------------+--------+-------+--------+ | | Embeddable | Remote | Cloud | Mobile | +------------------+------------+--------+-------+--------+ | Embedded Graph | X | | | | | Remote Graph | | X | | | | Service Provider | | | X | | | Mobile Graph | X | | | X | | Graph System | X | X | X | | +------------------+------------+--------+-------+--------+
Robert Dale On Tue, Oct 16, 2018 at 7:08 AM Stephen Mallette <[email protected]> wrote: > I think you're both missing the distinction I'm trying to make here. > > > JanusGraph is not remote-only. > > JanusGraph in the mode offered on IBM Compose is remote only. > > https://help.compose.com/docs/janusgraph-connecting-to-janusgraph > > > I didn't think DSE Graph was remote-only either. > > DSEGraph is remote-only. > > When I write "remote-only" I mean that you can't embed an instance, nor can > you host an instance in Gremlin Server yourself. You have no access to the > classes that would enable that. I would say that you can only connect to > these graphs over Gremlin Server protocols, but even that's not true. The > only real definition here is that these graphs accept Gremlin (scripts > and/or bytecode at this time) on requests and return results. I want a name > for these types of graphs because they represent an interesting new type of > graph that have a completely different model from what we've been used to > and what our documentation looks like. > > As I write this a little more clearly now I wonder if "Gremlin Service > Provider" is right. It sorta implies this cloud-based hosting or something > and DSE Graph sits in the middle on that in a way. What do we call a graph > that just accepts gremlin remotely and returns results. "Remote Graph > Systems"? "Remote Gremlin Graphs"? maybe it needs "remote" in it..... > > Does this make more sense now? thoughts? > > > I'm also for naming normalization across the TinkerPop. Here are some > other names out there: > > hmm - yeah...we could probably do better with that. perhaps a different > discussion..... > > > > > On Tue, Oct 16, 2018 at 3:45 AM Jorge Bay Gondra <[email protected] > > > wrote: > > > I think the name used in the providers > > <http://tinkerpop.apache.org/providers.html> section "TinkerPop-Enabled > > Graph Systems" is clear. An alternative would be "Gremlin-Enabled Graph > > Systems". > > > > El mar., 16 oct. 2018 a las 4:11, Robert Dale (<[email protected]>) > > escribió: > > > > > I like the name but not entirely sure I'm on the same page. JanusGraph > > is > > > not remote-only. I didn't think DSE Graph was remote-only either. > > > > > > I'm also for naming normalization across the TinkerPop. Here are some > > other > > > names out there: > > > Graph Systems - http://tinkerpop.apache.org/#graph-systems > > > Graph Database > > > TinkerPop-Enabled Providers - > http://tinkerpop.apache.org/providers.html > > > Data System Providers - > > > http://tinkerpop.apache.org/providers.html#data-system-providers > > > TinkerPop-Enabled Graph Systems > > > Graph Provider > > > > > > > > > Robert Dale > > > > > > > > > On Mon, Oct 15, 2018 at 1:35 PM Stephen Mallette <[email protected] > > > > > wrote: > > > > > > > I'm trying to come up with a name to describe graph providers like > > > Neptune, > > > > CosmosDB, DSE Graph, IBM Compose JanusGraph, etc. I've been calling > > them > > > > "server graphs" because they are "remote" only. They just accept > > Gremlin > > > as > > > > a request and return results. I don't really like "server graphs" > > though > > > - > > > > how does a "Gremlin Service Provider" sound? anyone have better > ideas? > > > > > > > > > >
