![]() Especially when we start to use ORM (Object Relational Mapping) frameworks to abstract from databases and operate on entities and between them. This comes with interesting issues and limitations. In short, we can say that there are no real connections-the database just gives us a direction to potentially find elements. It almost as simple as: Find me all ROWs in ROOMs table where id is 1 If the table has good indexing, it’s very fast, but the idea stays the same. The PropertyID of an entity is used to locate it in another table. The word find here represents the main idea: there is no direct link or connection. All you do is say that this column in a table is used to find a row in another table. It’s true that SQL allows us to represent relationships, but it’s very artificial-maybe even imaginary. In case we need many-to-many relationships (a well-known case), just create a join/pivot/many-to-many table and you’re fine. We have primary keys and even triggers which enforce these relations between elements in different tables. I can hear a valid question: what’s the difference with classic SQL? We’ve been doing relationships there for ages and they seem to work fine. Relation databases – we’ve be doing it for ages Graph databases allow you to store data in such representations. There are standards which you might like to follow: some allow you to put properties inside of an entity (e.g., property graphs), others insist on making every property an entity and connecting them with relationships (e.g., RDF or other semantic graphs). Graphs can be designed in different shapes and forms. What’s a graph? In general, it’s simple: treat relationships between entities, elements, and nodes as important as those elements themselves. Graphsīefore we go any further let’s set up a foundation. To some degree they’re correct, but let’s dig deeper to understand what GraphQL and graph databases have in common and how are they different. When conversation lands on graph databases most people say: But, here, we’re talking about graph databases, so let’s start with the basics. I’m sure there are a lot articles giving a great overview of GraphQL APIs and comparing them to REST/SOAP and/or RPC (continue the list with your personal favorite). The technology provides a simple and elegant method of implementing to APIs. Nowadays, you’ll see GraphQL used in a lot of production and high load projects-and for good reason. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |