Earlier quoted context omitted.
I think AWS already has a graph DB product. https://aws.amazon.com/neptune/
Is Neptune really on-par with Google Spanner?
Is dgraph?
Quitting Dgraph Labs
61–70 of 94 posts
Re: Quitting Dgraph Labs
#62Earlier quoted context omitted.
> 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…
I read those snippets and thought the same thing. This guy thinks he is god. 1000x engineer.
Deep familiarity with a complex code base is a thing and is not easily replicated. I have seen this first hand. In my day job - I work on a very popular but complex open source project and in my team there is a engineer who has been there since beginning and I am like second person after him.
I have noticed that when we get certain class of bugs from customers(and customers want fix NOW) that spans 2-3 layers of the project, only me and him can pick those bugs. Some decisions are there in the code that is not easy to figure out(like why it was done this way) and I have also seen engineers who are founders of this project - point design issues that I could not have thought (and I am doing this for 5 years!).
Can we hire someone new to provide design reviews that spans network, storage, kernel? May be - but engineers who created this thing and have been doing this for long time, have got really good at it. To me - some of them seem god like. I know they will probably suck same as me, if they had to start developing a new iOS app or write new game for Nintendo Switch.
Re: Quitting Dgraph Labs
#63Earlier quoted context omitted.
Do rockets sometimes blow up on the launch pad? Yes. Does that mean they shouldn't have tried to build a rocket ship? Have you tried to build a data layer engine? This kind of attitude is so one dimensional from my perspective... they are trying and it's hard to always be perfect when it comes to data. Inevitably if you're in the data game sometimes data loss happens, that's just the nature of the game. It's not blac…
The point is, when the rocket explodes on the launch pad you don't have the head of NASA saying "Well technically all the pieces of the rocket are still there, so technically we didn't lose it."
This is in the context of essentially a bug bounty for data loss issues that they were running… sounds like a NASA administrator saying something like "show us how our rocket will fail"
Re: Quitting Dgraph Labs
#64I worked for a company last year that chose Dgraph as its primary data store.
Thanks to Dgraph's query language, we were able to implement a GraphQL API server that had no resolvers and no need for dataloader—the n+1 problem simply couldn't occur! It was like magic.
Interestingly enough, we had been working with a salesperson from Dgraph Labs who was affected by the June layoff—along with the rest of the sales staff and CEO—right as we were about to pay for Dgraph Cloud! For a solid week we seriously debated switching to another database, but eventually decided to go with Dgraph Cloud anyway—telling ourselves we would self-host if Dgraph Labs folded.
I ended up leaving in November, but I think I know what my former team will be doing over the next few sprints!
I wish Manish and crew all the best, and hope they succeed in their new endeavor. Dgraph is pretty dang cool.
Re: Quitting Dgraph Labs
#65Earlier quoted context omitted.
> 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…
It sure seems like you used to work there since you're making specific critiques about company culture and decisions that only someone internal would know. And you're taking statements like "lost a couple of deals last quarter due to engineering challenges" as being a personal slight against the engineering team when an impassioned observer would not really see it that way. I don't know the specifics of Dgraph's fail…
The CEO's statements come across as insulting to anyone who isn't blinded by founder worship. I'm saying this as someone who did not even know about dgraph before today.
Presuming the GP must be a disgruntled employee because he can read a Glassdoor review is just naive.
Re: Quitting Dgraph Labs
#66I 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?
I'm not sure what "eat section 13 of Mongo's license" means, but if you're asking whether you should self-host Mongo or pay Mongo Corp to host it, I would say the latter. It's not that expensive, they have a nice management UI, failover, performance hints, backups etc.. And I say this as someone who doesn't like Mongo DB and believes it's almost always the wrong technology for business to use. But if you're using it,…
> I'm not sure what "eat section 13 of Mongo's license" means
Buncha weeks ago I had a paranoid fit about the legalities of this app I wanna try to launch. I read some conserning things about the MongoDB license, mainly that the open source initiative didn't approve it bc Mongo pulled out. I read the controvertial paragraph and now I am 80% convinced that I'm not allowed to self-host a MongoDB server for my own profit.. I'd have to pay.. which why should I when SQL is free. BUT I DON'T WANNA USE SQL. And frankly MongoDB wasn't living up to the stresses I wanted from it but Dgraph does.
Asking for help on stackexchange didn't do me any better https://law.stackexchange.com/questions/74510/can-i-use-mong...
I was planning on self-hosting my Dgraph database anyways, and if this app actually ends up being something, I would beable to calculate milestones that I'd need to reach before considering upgrading to Dgraph Enterprise. Now I'm more worried about future support. Is Dgraph going to be sunsetted, and will I have the features I might need in the future. IDK I think I just freaked out about something I didn't understand, sry guys.
Re: Quitting Dgraph Labs
#67Earlier quoted context omitted.
I read those snippets and thought the same thing. This guy thinks he is god. 1000x engineer.
Deep familiarity with a complex code base is a thing and is not easily replicated. I have seen this first hand. In my day job - I work on a very popular but complex open source project and in my team there is a engineer who has been there since beginning and I am like second person after him. I have noticed that when we get certain class of bugs from customers(and customers want fix NOW) that spans 2-3 layers of the…
[deleted]
Re: Quitting Dgraph Labs
#68Earlier quoted context omitted.
The point is, when the rocket explodes on the launch pad you don't have the head of NASA saying "Well technically all the pieces of the rocket are still there, so technically we didn't lose it."
This is in the context of essentially a bug bounty for data loss issues that they were running… sounds like a NASA administrator saying something like "show us how our rocket will fail"
On the contrary, it sounds like a cover-up. Looking into the Github Issues, every-time someone does demonstrate data loss, the admins ignore it, argue it isn't data loss, or in one case, claim that the person who showed data loss is a disgruntled ex-employee (???)
https://github.com/dgraph-io/badger/issues/570#issuecomment-...
https://discuss.dgraph.io/t/bounty-challenge-prove-that-badg...
Given that the former CEO is here right now accusing people of shilling while he scrubs unpleasant details from his past posts, I'd say this just appears to be a dead, toxic startup.
Re: Quitting Dgraph Labs
#69Earlier 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…
Glad you quoted statements from @mrjn / Manish's original post because it looks like he edited a bunch of those out of his post.
And yes it sounds not only like he's throwing his engineering team under the bus but also thinks they were incompetent which is beyond something any C* level person would be silly enough to write.
Re: Quitting Dgraph Labs
#70Terrible 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.
Is it really that bad? *cough* CockroachLabs / CockroachDB *cough*
I like that name, cockroaches are difficult to kill ;)