Build your next app with a graph database
11–20 of 58 posts
Re: Build your next app with a graph database
#12Currently migrating off a graph database and back to a relational one. It's been a bit of a nightmare. I think there are legitimate use cases for the tech. Yours probably isn't it.
Re: Build your next app with a graph database
#13Please don't. Graph databases have only a few niche use cases which, even then, in most occasions, can be adequately covered by a relational database.
Re: Build your next app with a graph database
#14My only gripe with it so far is their documentation could use some updating. The onboarding path isn't real straight forward. I've had to jump around to different parts of the documentation and piece together stuff to get started.
Re: Build your next app with a graph database
#15This reads more like a sermon than a technical article.
Re: Build your next app with a graph database
#16Re: Build your next app with a graph database
#17I wonder if anyone can speak to how Hasura's approach compares to designing an architecture around a pure graph database?
Re: Build your next app with a graph database
#18"Relational databases: a software engineering fail
...
That you were taught relational databases at all is an accident. It's simply that they are an early tech that became widely used, so your teacher knows about them, and, importantly, that they are a dream to teach."
What. Really?
Re: Build your next app with a graph database
#19"Relational databases: a software engineering fail" Hard to take this piece seriously with a headline like this.
Re: Build your next app with a graph database
#20From the article: "Relational databases: a software engineering fail ... That you were taught relational databases at all is an accident. It's simply that they are an early tech that became widely used, so your teacher knows about them, and, importantly, that they are a dream to teach." What. Really?