message queue persistence attempt

Recently, I have been synchronizing the organizational structure. For example, it needs to be synchronized to enterprise WeChat, DingTalk, Ali mailbox, etc. However, I found that the scalability is a bit problematic, that is, every time I do a new synchronization, I need to write some repetitive code. Especially Dingding synchronization, because of the concept of branch offices. Three companies in DingTalk need to be synchronized. Because the current logic is that it still needs to be compared with the organizational structure in DingTalk. Because some DingTalks already have an organizational structure, they are only maintained manually, not synchronized with programs.

Now I think of a solution, which is based on the message queue. by subscription. rather than a producer-consumer approach. Because the organizational structure synchronization is generated in the hr system, and then synchronized to various apps.

There is also the need to persist to the database to facilitate future queries.

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=325121616&siteId=291194637
Recommended