Skip to main content

Needs for Graph Database

Needs for Graph Database:

We are living in the era of data, data is treated more precise than gold and platinum. Most of the enterprises are trying to get more insight about the data they have it as an operational / warehouse / analytical. 

graph example

 Ref.: https://dist.neo4j.com/wp-content/uploads/graph-example.png

To get more insight into the data, it is required to see the relationship among the data points. The challenge is how to establish the relationship among data points and the answers is Graph database. Relational databases can't help to establish the relationship among data points, due to their rigid schema, and consistent schema.

Relational Database issues for data set:

Number of Joins: 

While fetching data from relational databases, we join many tables, these joins are complex, and consume considerable amount of computing resources, which increase the query response times.

Self- joins:

For database ware house / business intelligence systems using RDBMS, self-JOIN are common for hierarchy and tree representation of data such as employee, and manager. When we traverse relationship by joining themselves, it results in an inefficient approach to retrieve the data.

Schema Changes:

Relational databases are not designed for frequent schema changes, and pivots. We are living in the era of agility, which requires frequent schema changes and flexibility.

Slow Queries:

Even though expert DBA put all efforts, use all tricks such as materialized view (computing past results ahead of time) , de normalize the entities to speed up the query, still queries are not fast enough to server the current business needs.

Graph database has the ability to address the issues, challenges of the RDBMS, let us explore 

Benefits of Graph database:

Agility:

In current agile software development process / method, test-driven development is an essential part. Modern Graph databases have features to server friction-less development, and graceful system maintenance.

Flexibility:

As we all know the speed does matter in current throat cut competition for the business, IT and data architect has to move at the speed of business. The structure and schema of graph data model is flexible and run with the needs of business. The IT team can add to the features require to the existing graph structure without endangering existing functionality.

Performance:

Graph database can deliver consistence performance even though the data grows every year. Graph database can handle very efficiently the data relationship. Graph database can deliver performance by several magnitude compared to RDBMS.

Ref.: https://neo4j.com/blog/why-graph-data-relationships-matter/

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

MySQL InnoDB cluster troubleshooting | commands

Cluster Validation: select * from performance_schema.replication_group_members; All members should be online. select instance_name, mysql_server_uuid, addresses from  mysql_innodb_cluster_metadata.instances; All instances should return same value for mysql_server_uuid SELECT @@GTID_EXECUTED; All nodes should return same value Frequently use commands: mysql> SET SQL_LOG_BIN = 0;  mysql> stop group_replication; mysql> set global super_read_only=0; mysql> drop database mysql_innodb_cluster_metadata; mysql> RESET MASTER; mysql> RESET SLAVE ALL; JS > var cluster = dba.getCluster() JS > var cluster = dba.getCluster("<Cluster_name>") JS > var cluster = dba.createCluster('name') JS > cluster.removeInstance('root@<IP_Address>:<Port_No>',{force: true}) JS > cluster.addInstance('root@<IP add>,:<port>') JS > cluster.addInstance('root@ <IP add>,:<port> ') JS > dba.getC...
Post a Comment
Read more

InnoDB cluster Remove Instance Force | Add InnoDB instance

InnoDB cluster environment UUID is different on node: To fix it stop group replication, remove instance (use force if require), add instance back Identify the node which is not in sync: Execute following SQL statement on each node and identify the node has different UUID on all nodes. mysql> select * from mysql_innodb_cluster_metadata.instances; Stop group replication: Stop group replication on the node which does not have same UUID on all nodes. mysql > stop GROUP_REPLICATION; Remove instances from cluster: Remove all secondary node from the cluster and add them back if require. $mysqlsh JS >\c root@<IP_Address>:<Port_No> JS > dba.getCluster().status() JS > dba.getCluster () <Cluster:cluster_name> JS > var cluster = dba.getCluster("cluster_name"); JS >  cluster.removeInstance('root@<IP_Address>:<Port_No>'); If you get "Cluster.removeInstance: Timeout reached waiting......" JS > cluster.removeInstance(...
2 comments
Read more

Oracle E-Business Suite Online Patch Phases executing adop

Following description about Oracle E-Business Suite is high level and from documentation https://docs.oracle.com/cd/E26401_01/doc.122/e22954/T202991T531062.htm#5281339 for in depth and detail description refer it. The online patching cycle phases: Prepare Apply Finalize Cutover Cleanup Prepare phase: Start a new online patching cycle, Prepares the environment for patching. $ adop phase=prepare Apply phase: Applies the specified patches to the environment. Apply one or more patches to the patch edition. $ adop phase=apply patches=123456,789101 workers=8 Finalize phase: Performs any final steps required to make the system ready for cutover. Perform the final patching operations that can be executed while the application is still online. $ adop phase=finalize Cutover phase: Shuts down application tier services, makes the patch edition the new run edition, and then restarts application tier services. This is the only phase that involves a brief ...
Post a Comment
Read more