mrjn

24 ms·

211.
by mrjn 7y ago
For e-commerce, a big one is recommendations. But graphs are already known for that. We see a lot of usage of Dgraph among developers who are building apps with social data. Or, platforms where they need to unite multiple different data sou
212.
by mrjn 7y ago
Hey, founder of Dgraph Labs here. If you are interested, we would love to consider you for a role at Dgraph. Feel free to reach out to me at Manish at Dgraph.io.
213.
by mrjn 7y ago
(author of Badger here) Thanks for sharing the link! Really excited about this release. It contains a bunch of features directly needed to run multi-node, synchronous replicas of Dgraph. In particular, the StreamWriter API was written to st
214.
by mrjn 8y ago
(author of Dgraph) We use specific libraries from Bleve to do, for e.g., full-text tokenization and such. But, we use our own indexing and storage mechanism, not Bleve's.
215.
by mrjn 8y ago
Not to nitpick here, but Google's cloud libraries and Amazon's AWS libraries work because there're probably a dedicated team of engineers who're assigned to these projects, considering cloud platforms are supposed to mak
216.
by mrjn 8y ago
I see. Then I guess there's a different model that can more accurately represent the idea of giving certain well-written/actively-maintained/popular packages a special platform than others to make it more enticing for wider c
217.
by mrjn 8y ago
As mentioned down in this thread, the key-val would be bytes-bytes or string-bytes. While this is more expensive in terms of CPU, it has the advantage that the size of elements in the cache are carefully understood and do not need the cost
218.
by mrjn 8y ago
Arrr... Sorry about that. That was my idea, so my bad. We will get rid of the pop up banner.
219.
by mrjn 8y ago
> Godoc.org is that platform, it serves the purpose. Godoc.org is great. But (beyond documentation) it is at best a search engine, providing equal platform to all libraries however production ready or broken they might be. Unless I'
220.
by mrjn 8y ago
(co-author here) Thanks for sharing this post! We've elaborated the various issues we encountered trying to use a concurrent LRU cache in Dgraph and our dissatisfaction at existing choices which fail to provide memory management, high
221.
by mrjn 8y ago
(co-author here) The number of Go libraries tend to be just slightly below the number of their users (dramatically speaking). Libraries are hardened by repeated usage by many different users who each bring their own special use cases and im
222.
The State of Caching in Go(blog.dgraph.io)
27 points by mrjn 8y ago|5 comments
223.
by mrjn 8y ago
Slightly old post, but we did some benchmarks couple of years ago: https://blog.dgraph.io/post/benchmark-neo4j/ We also get to hear benchmark conclusions from users who tried out Neo4j, Janus, Datastax DSE Graph,
224.
by mrjn 8y ago
Dgraph exposes both HTTP endpoint and gRPC endpoint. All our official clients use the gRPC endpoint, including Go, Java, NodeJS client. https://docs.dgraph.io/deploy#ports-usage
225.
by mrjn 8y ago
Yes, I meant denormalize. Thanks.
226.
by mrjn 8y ago
I haven't. But, the design is the same. Graph layer on top of another DB, because they didn't want to invest in building a native graph DB. In general, that approach doesn't lead to good performance, as I explained in the blo
227.
by mrjn 8y ago
Not just you, a lot of Dgraph users appreciate the intuitive model of GraphQL+- (modification on GraphQL), and how it fits naturally with JSON and apps. When I started in 2015, I didn't imagine that our decision to use GraphQL would be
228.
by mrjn 8y ago
It's a good start to solving an array of problems when considering building a low-latency arbitrary depth graph DB. Dgraph does these: 1. It shards by predicate so a full join can be executed by one server. 2. Storing SPO as a record (
229.
by mrjn 8y ago
I don't want this to become a flame war between SQL and Graph. But, we see a lot of developers come from SQL to Dgraph, because the join performance of SQL gets worse as the data size grows, and so devs have to resort to doing aggressi
230.
by mrjn 8y ago
No concrete plans yet, but that's a direction we want to go in.
231.
by mrjn 8y ago
Badger don't care! https://www.youtube.com/watch?v=4r7wHMg5Yjg
232.
by mrjn 8y ago
Now consider doing this in a distributed setting, with SQL tables splits across dozens or 100s of machines (see Facebook TAO).
233.
by mrjn 8y ago
One of the TLs was a T7. Got overruled by T8 :-). As Google is growing, there are many T7s around. So, you really need T8 and above to actually get something out of the door, when it comes to impacting web search. P.S. Dgraph is Apache lice
234.
by mrjn 8y ago
That's an impressive quote! Nails it.
235.
by mrjn 8y ago
That was the exact issue Google found itself in. Every OneBox had their own backend, which meant many different teams were involved in running and maintaining them. Now, with the graph serving system in place, all they need to do is to slap
236.
by mrjn 8y ago
We recently made this image, inspired by my favorite movie. It's licensed under CC-by-ND. https://twitter.com/dgraphlabs/status/1088516069852012544 Feel free to use it! :-)
237.
by mrjn 8y ago
Dgraph usages are quite wide-spread. It is being used for typical graph cases, like recommendation engines, real-time fraud detection, adtech, fintech uses, etc. The design is very well suited for just building apps (scalable, flexible sche
238.
by mrjn 8y ago
Consider Dgraph :-). https://blog.dgraph.io/post/neptune/
239.
by mrjn 8y ago
Consider [sort all comedy movies by rating]. Such queries happen on a daily basis on movie sites like IMDB or Rotten Tomatoes. The only way to avoid joins is when you specialize your data to a particular vertical. Therefore, your flat table
240.
by mrjn 8y ago
I'd suggest starting with https://docs.dgraph.io/get-started/ , and then going to https://tour.dgraph.io . It gives you all you need to understand the query language (based on GraphQL) and get you up to

More ›