3 ms·
This blog post explain the business needs that Dgraph is solving for: https://dgraph.io/blog/post/how-dgraph-labs-raised-series-a/ https://dgraph.io/blog/post/h
by mrjn 6y ago
This blog post explain the business needs that Dgraph is solving for: https://dgraph.io/blog/post/how-dgraph-labs-raised-series-a/ https://dgraph.io/blog/post/how-dgraph-labs-raised-series-a/
My comments about Google were accurate. I want to avoid saying anymore on that topic, because that's not my point here.
- h0l0cube 6y agoThanks for the link. It does indeed illuminate business utility. A problem (for you, not me), is that people might realize they need a dedicated graph database down the track after they've built their infrastructure around a typical RDBMS. Might be a foolish question, but do you have any tooling/strategies that help an org transition to Dgraph, or use it parasitically? Seems if an org could get a taste of what Dgraph could do for them, they'd be more likely to invest in it. > My comments about Google were accurate. Accuracy wasn't the issue. I look forward to seeing where Dgraph goes, and I might give it a try in the future.
- mrjn 6y agoSo far we have been focused on delivering to folks who already are convinced about graphs. We absolutely need to do a better job at selling Dgraph and showing value early on to the orgs who don't yet understand the need for a graph solution. Our foray into GraphQL is a step in that direction, but we need to do more education.