41–50 of 94 posts
I just refactored my whole app from MongoDB to DGraph... Guys I really like this idea I don't want to abandon it. What should I do: eat section 13 of Mongo's license, or try to maintain a database server myself?
Or understand that MongoDB's license is kind of a necessary evil that I guarantee DGraph will likely implement at some point. Amazon's embrace and extinguish approach is too successful to ignore.
I just refactored my whole app from MongoDB to DGraph... Guys I really like this idea I don't want to abandon it. What should I do: eat section 13 of Mongo's license, or try to maintain a database server myself?
Earlier quoted context omitted.
Manish here. I don't know who you are or what your motivations are. Glassdoor Reviews are anonymous (read trolls) and a lot of them were created post the layoffs, to create a story that would take the blame away from the hired CEO. Read between the lines about why the layoffs happened in the first place. If not, read this: https://www.glassdoor.com/Reviews/Employee-Review-Dgraph-Lab... When you have nothing to say ab…
> I don't know who you are or what your motivations are. I'm a rubbernecker passing by a car crash. I have no other motivations. I don't know you personally or anyone who works at Dgraph. I'm piecing together a guess of the culture from what's available externally. I would love to read the details when you're ready to share. Editing to say that the only reason I remembered the blog was because there were multiple par…
Doesn't come as much of a surprise really. $employer had a need for some of the bits of Dgraph that are unfortunately hidden behind a paywall (bits that IMHO should have been in the community version as they were not particularly enterprisey, but hey such is life). A frustrating conversation with Dgraph sales-droid ensued: Us: We need access to X/Y/Z features, but on-prem Droid: But Cloud Us: Cloud = No-go because X/…
Earlier quoted context omitted.
Manish here. I don't know who you are or what your motivations are. Glassdoor Reviews are anonymous (read trolls) and a lot of them were created post the layoffs, to create a story that would take the blame away from the hired CEO. Read between the lines about why the layoffs happened in the first place. If not, read this: https://www.glassdoor.com/Reviews/Employee-Review-Dgraph-Lab... When you have nothing to say ab…
> I don't know who you are or what your motivations are. I'm a rubbernecker passing by a car crash. I have no other motivations. I don't know you personally or anyone who works at Dgraph. I'm piecing together a guess of the culture from what's available externally. I would love to read the details when you're ready to share. Editing to say that the only reason I remembered the blog was because there were multiple par…
Those were not my words. Those were the literal words used by my Engineering manager out of desperation to convey to me that the team needs my help in solving these problems.
I'm not sure why you would take these as "throwing the team under the bus." This is actually expected -- given I wrote a lot of that code, and was the most senior engineer in the whole company.
This was the result of that effort, btw:
https://dgraph.io/blog/post/manual-memory-management-golang-...
And we had the best team we could build with the resources we had access to. 4 of my team members have created 3 companies -- one is YC, one has a wild acquisition offer, and one is Sequoia-backed. And they all seem to like me a lot.
https://github.com/dgraph-io/badger/issues/578 titled "Badger unable to return data after value log GC" vs https://github.com/dgraph-io/badger/issues/570#issue-3621168...
> However, if the bug only causes Badger to not return data, and the data is fully recoverable by an easy fix to the code -- that's technically not a data loss (See Badger unable to return data after value log GC #578).
Never let this person store your data.
Terrible new name though. Outcaste manages to both combine the negative associations of being a reject and the Indian caste system, and permanently remind users of the project's troubled history.
*cough* CockroachLabs / CockroachDB *cough*
Earlier quoted context omitted.
Open sourcing their code would be a terrible idea for the business unless they opted for a Elastic/MongoDB style license where you are prohibited from offering a cloud version of the code. Because you know AWS would be circling this news very closely for another product to add to their lineup.
I think AWS already has a graph DB product. https://aws.amazon.com/neptune/