- A graph is an abstract datatype used to model data between ‘objects’.
- Edge is the relationship between the objects.
- Vertex is an object containing data
- Increase efficiency for certain datasets
1 Like
1- What is a graph?
It is an abstract structure used to visually model or represent data or objects and illustrate the relationships / connections between them.
2- What is an edge?
The relationships between objects are known as edges (or lines).
3- What is a vertex?
The objects are also known as vertices (or nodes) and contain the properties related to that entity – anything the business needs to keep track of. It is the equivalent of a row in a relational database.
4- Why would we want to use a graph database instead of a normal SQL database?
They are more efficient for some datasets especially when deeper searches need to be constructed.
1 Like
- A graph database uses nodes or vertices to function as records in a SQL database. The nodes are connected by lines or edges which record the relationships between nodes.
- An edge is the relationship between the 2 nodes it connects. It is like a foreign key in a SQL database.
- Vertices are objects such as people or artifacts (generally have properties).
- Graph databases are the perfect representation for those that contain large amounts of relationships between objects.
1 Like
Graph databases are an abstract data type consisting of objects, called nodes or vertices. Each node will contain specific informational attributes or properties of the node data. the nodes are interconnected using edges (lines) that define the relationships similar to a foreign key in a DBMS. Graph Databases are highly useful when data has a lot of relationships and the users need to do multilevel queries about the data, such as corporate structures of large organizations.
1 Like
1- What is a graph : A data type used to model data using nodes or vertex and lines or edges to define relationship the nodes.
2 - What is an edge : an edge defines te relation between nodes in a graph database (like an id)
3 - What is a vertex : A node with its properties (cfr. record in SQL)
4- Why would we want to use a graph database instead of a normal SQL database :
this kind of database makes complex searches easier
1 Like
- A graph is an abstract data type typically used to model data that contains objects (referred to as nodes or vertices), and some sort of relationship between those objects (lines or edges).
- An edge is used to describe the relationships between the objects contained in the database. Comparable to a foreign key in a relational database.
- Is a node, contain the data
- Graph databases are the perfect representation for those that contain large amounts of relationships between objects.
1 Like
OK, before I say anything I am going to backup my information with this class/relationship break down of a configuration management database, CMDB. It’s RDBMS @ http://www.hudsky.com/Unix/cmdb/code/9.1/index.html
The take away from this lecture or the argument that a graphical database is better when relationshisp of objects are in focus. I am going to have to disagree. Again, please accept my sencere apologies. I am here to learn and add to the discussion.
“Graph databases are the perfect representation” is only true for data visualization. OK, fine, it’s pleasing to the eye. However, that does not mean that a RDBMS can’t do well or better with relatiobships then a graph database. This opinion is my opinion only and comes from over 20 years of experience in the field.
A relationship in a “normal” SQL database can and is represented as a record of relationship and is used in large datasets. It can be used in a hierachial way. For example in the link above I have full list of classes used by the CMDB where the BMC_BaseRelationship is a class with child relationships defined. The child relationships like Dependency, HostedSystemComponents, or Impact relationbships inherit its base attributes from the parent. So if I wanted to see how many relationships exist between a host (ComputerSystem) and an application, I can query the depency relationship and get them in a number any human can understand. In a graphical database you can’t see the volume of data effectively. Sure, you can look at the foam created by the waves of an ocean and easily describe it as “lots of bubbles”, but you have no idea ‘how many’ bubbles you have there. These abstact data types have no tangent to form a specific report that’s tied to a value. They’re pretty to look at in management meetings where some guy with a fancy tie can show that data to another guy with even fancier tie, but for the data miners that I’ve worked with so far this type of data has zero value. I am looking forward what to what this course will bring to see how a graph database adds value to today’s computing.
I am going to forgo using the made up terminology of edge, vertex and graph because I simply see them as people just creating more and more useless products just like the sea of crypto currency projects. Stop it already and pick one 
. I did. Use a RDBMS database even if you have to pay for the license. if you know what it’s like to go to a job interview nowadays. it’s a sea of acronyms that can make someone sound like they know what they’re doing just by spewing the buzzwords around. Job postings have list of 30 technologies, PhD in quantum physics and, oh btw it pays 25$/hour. Now they’re peppered with new terminologies that do the same thing, but underwent a name change because marketing said it would help with name recognition.
I know I can’t stop the tsunami and that there will be new technologies coming out that basically do the same thing under a diffent name. I just would love the Relationsional over NoSQL or Graph what ever war to be over. And as always, I am looking forward to what muj kámoš Ivan has to say in the courseware. 
Daniel Hudsky
1 Like
Excellent answer, It’s easy to understand. Please keep them like that 
Carlos Z.
1 Like
Graph Database - Reading
-
A graph store, using nodes to store entities, and navigate relationships.
-
An Edge store relationships between entities. Always have a start node, end node, type and direction.
-
A Vertex is an entity like a person, place or thing relevant to a data that represent the relationship between the nodes.
-
We would want to use graph database instead of SQL database because in graph database relationships take priority. The data model are much more simpler yet more expressive than the ones you’d produce with relational databases or NoSQL stores.
1 Like
1.A graph is an abstract data type typically used to model data that contains objects (referred to as nodes or vertices), and some sort of relationship between those objects (lines or edges).
- An edge is the relationship between the 2 nodes it connects. It is like a foreign key in a SQL database.
3.A single object that is part of the whole data model or Graph. They are also known as Nodes and are connected by edges.
- The ability to directly state the relationship between two objects within a graph database provides a strong advantage over relational database systems for certain datasets.
1 Like
-
A graph is a data type that contains nodes/vertices with lines/edges between them defining some sort of relationship.
-
An edge represents a relationship between nodes.
-
A vertex is a node in a graph database.
-
A graph database would be used instead of a normal SQL database for instances where the ability to state a relationship between two objects is required. There are also cases where a graph database may provide increased efficiency in searches.
1 Like
- A graph is an abstract data type used to model data that contains objects and relationships between those objects.
- An edge in a graph database represents the relationships between objects.
- A vertex is the representation of an object in a graph database.
- Graph databases are good for datasets with a lot of complex relationships and are more efficient when complex queries are required.
1 Like
1.) What is a graph?
A graph is an abstract data type typically used to model data that contains objects (referred to as nodes or vertices), and some sort of relationship between those objects (lines or edges).
2.) What is an edge?
These are use to describe the relationships between the objects contained in the database, and in most they can be compared to the foreign key column of a row in a RDBMS.
3.) What is a vertex?
It’s the node which contains the data
4.) Why would we want to use a graph database instead of a normal SQL database?
The ability to directly state the relationship between two objects within a graph database provides a strong advantage over relational database systems for certain datasets. Namely, those that contain a large amount of relationships within the data. Graph databases may also offer increased efficiency for searches in some cases. The best example of this is when a business needs to perform a search that is more than one level deep. As an example, let’s consider a database storing corporate structure information.
1 Like
- A graph is an abstract data type used to model data that contains objects and some sort of relationship between those objects.
- An edge describes the relationship between two objects.
- A vertex is an object that belongs to a data model.
- If you have a database with a lot of relationships a graph database allows you to directly state the relationship between two objects.
1 Like
- It is a graphical representation of data groups
- It is a connection between 2 data nodes
- It is a node of data
- It can sometimes establish relationships between data more easily.
2 Likes
not sometimes, IT WILL stablish the relationships between the data more easily. (When it comes to appreciate the entire relationships between different tables in a more easy to read way, graph databases can be the best approach)
If you have any more questions, please let us know so we can help you! 
Carlos Z.
1 Like
- A graph is a data type that contains objects and those objects are related between each other.
- The edge describes the relation between the objects.
- A vertex is a node which is connected by edge to another node.
- We will use graph db when we need to find (search) data deeper than just one level
1 Like
- What is a graph?
a graph is an abstract data type typically used to model data that contains objects (referred to as nodes or vertices), and some sort of relationship between those objects (lines or edges).
- What is an edge?
It is the relationship between the nodes can be represented by lines in a diagram.
- What is a vertex?
A vertex is the node holding the object and it’s properties.
- Why would we want to use a graph database instead of a normal SQL database?
If you have data that has many relationships and you need to query multiple levels deep.
1 Like
1,
Graph is an abstract data type, used to model data and relationships
2,
Edge is a relationship between objects in a graph data
3,
Vertex is an object in a graph data, also known nodes
4,
When we want to present in a business which is more than one level deep in graph data is easier and clearer to see data and all additional information.
1 Like
- a graph is a DB which uses graph structures for semantic queries with nodes, edges and properties to represent and store data.
- an edge is is found between nodes and represents the relationships between the objects within the nodes (similar to foreign keys in RDBMS)
- a vertex or vestices represent objects input into the database. People and their tracked characteristics for instance.
- we would want to use a graph database instead of a normal SQL database when we will be querying the DB for data that is deeper than first level. It is better suited to represent data that have relationships when there is a large amount of data, and affords more efficient searches in most cases.
1 Like