Redisgraph graphic database multi activity design scheme

at present CMDB Use RedisGraph Store various relationship mapping data , The importance of data is self-evident , So data disaster prevention 、 High performance and high availability are very important .

The current situation

• RedisGraph It is a single node operation , There is data disaster prevention 、 High availability 、 The defect that the performance is not easy to expand
• stay CMDB In the system RedisGraph Application flow chart

The current situation is improved

• In order to solve data disaster prevention 、 High availability 、 High performance requirements ,RedisGraph Design is primary and secondary （1 Lord 2 from ）、 Read write separation architecture
• After improvement RedisGraph Architecture design

High availability

• Mainly through the master-slave mode , When the Lord redis When the data changes , Real time synchronization to from redis
• When the Lord redis When problems occur and the service cannot be continued , The sentry turned from redis Act as master redis Continued provision of services
• High availability design normally

• When something goes wrong

High performance

• The performance is mainly achieved by configuring the read-write ratio through the proxy layer , There can be master be responsible for CUD operation ,slave Realization R operation
• The high-performance design scheme is normal as follows

• When something goes wrong

remarks

• The scheme design does not affect cmdb Existing development implementations , Don't implement code for business requirements , Just change the graphic database link information .
• If there is no special need , It can be omitted. VIP, Direct link Proxy It's fine too .