Integrated entity view across distributed systems
Methods, systems, and computer program products for a customer relationship management (CRM) system are provided herein. Embodiments presented herein provide for exchange of data between disparate, distributed systems; subscribe to and/or publish customer data change event; creation of master records for consumers using static and streaming sources; providing data provenance, auditing capabilities, and queries across multiple tenants and third party systems. Embodiments provide a single view of a customer in a distributed system environment.
1. A method, comprising:
publishing, by a computing device, a first patron data change event under a first publication rule, and a second patron data change event under a second publication rule, wherein the first patron data change event and the second patron data change event correspond to a same patron and are published on a multi-tenant bus configured to be accessed by a plurality of organizations associated with a same entity, wherein the first patron data change event corresponds to a first organization associated with the same entity and corresponds to a first type of service, and wherein the second patron data change event corresponds to a second organization associated with the same entity and corresponds to the first type of service; determining, by the computing device, a first rule to subscribe to the first patron data change event, and a second rule to subscribe to the second patron data change event; receiving, by the computing device, the first patron data change event subscribed under the first subscription rule, and the second patron data change event subscribed under the second subscription rule, the first patron data change event being isolated from the second patron data change event; and sending, by the computing device, a transmission comprising information based on the received first patron data change event;
deleting, by the computing device, the published first patron data change event and the published second data change event after a period of time.
2. The method of claim 1 , further comprising: adding, by the computing device, at least one record to the first patron data change event according to the first publication rule.
3. The method of claim 1 , wherein the first patron data change event is received under the first subscription rule by applying a first filter criteria.
4. The method of claim 1 , wherein the first patron data change event is published under a first publication rule by applying a second filter criteria.
5. The method of claim 1 , wherein a third data source subscribed to the first patron data change event at one time point of the period of time.
6. The method of claim 1 , wherein the first patron data change event is a business event.
7. A system, comprising:
a memory;
a processor coupled to the memory and configured to, based on instructions stored in the memory: publish a first patron data change event under a first publication rule, and a second patron data change event under a second publication rule, wherein the first patron data change event and the second patron data change event correspond to a same patron and are published on a multi-tenant bus configured to be accessed by a plurality of organizations associated with a same entity, wherein the first patron data change event corresponds to a first organization associated with the same entity and corresponds to a first type of service, and wherein the second patron data change event corresponds to a second organization associated with the same entity and corresponds to the first type of service; determine a first rule to subscribe to the first patron data change event, and a second rule to subscribe to the second patron data change event; receive the first patron data change event subscribed under the first subscription rule, and the second patron data change event subscribed under the second subscription rule, the first patron data change event being securely isolated from the second patron data change event; and send a transmission comprising information based on the received first patron data change event;
deleting, by the computing device, the published first patron data change event and the published second data change event after a period of time.
8. The system of claim 7 , wherein the processor is further configured to: add at least one record to the first patron data change event according to the first publication rule.
9. The system of claim 7 , wherein the first patron data change event is received under the first subscription rule by applying a first filter criteria.
10. The system of claim 7 , wherein the first patron data change event is under a first publication rule by applying a second filter criteria.
11. The system of claim 7 , wherein the processor is further configured to: delete the published first patron data change event and the published second data change event after a period of time.
12. The system of claim 7 , wherein a third data source subscribed to the first patron data change event at one time point of the period of time.
13. The system of claim 7 , wherein the first patron data change event is a business event.
14. A non-transitory computer-readable apparatus having instructions stored thereon that, when executed by a computing device, cause the computing device to perform operations comprising: publishing, by the computing device, a first patron data change event under a first publication rule, and a second patron data change event under a second publication rule, wherein the first patron data change event and the second patron data change event correspond to a same patron and are published on a multi-tenant bus configured to be accessed by a plurality of organizations associated with a same entity, wherein the first patron data change event corresponds to a first organization associated with the same entity and corresponds to a first type of service, and wherein the second patron data change event corresponds to a second organization associated with the same entity and corresponds to the first type of service, determining, by the computing device, a first rule to subscribe to the first patron data change event, and a second rule to subscribe to the second patron data change event; receiving, by the computing device, the first patron data change event subscribed under the first subscription rule, and the second patron data change event subscribed under the second subscription rule, the first patron data change event being securely isolated from the second patron data change event; and
sending, by the computing device, a transmission comprising information based on the received first patron data change event;
deleting, by the computing device, the published first patron data change event and the published second data change event after a period of time.
15. The non-transitory computer-readable apparatus of claim 14 , further comprising: adding, by the computing device, at least one record to the first patron data change event according to the first publication rule.
16. The non-transitory computer-readable apparatus of claim 14 , wherein the first patron data change event is received under the first subscription rule by applying a first filter criteria.
17. The non-transitory computer-readable apparatus of claim 14 , further comprising: deleting, by the computing device the published first patron data change event and the published second data change event after a period of time.
18. The non-transitory computer-readable apparatus of claim 14 , wherein a third data source subscribed to the first patron data change event at a time point of the period of time.
19. The non-transitory computer-readable apparatus of claim 14 , wherein the first patron data change event is a business event;
publishing, by a computing device, a first patron data, change event under a first publication rule, and a second patron data change event under a second publication rule, wherein the first patron data change event and the second patron data change event correspond to a same patron and are published on a multi-tenant bus configured to be accessed by a plurality of organizations associated with a same entity, wherein the first patron data change event corresponds to a first organization associated with the same entity and corresponds to a first type of service, and wherein the second patron data change event corresponds to a second organization associated with the same entity and corresponds to the first type of service; determining, by the computing device, a first rule to subscribe to the first patron data change event, and a second rule to subscribe to the second patron data change event; receiving, by the computing device, the first patron data change event subscribed under the first subscription rule, and the second patron data change event subscribed under the second subscription rule, the first patron data change event being isolated from the second patron data change event; and sending, by the computing device, a transmission comprising information based on the received first patron data change event;
deleting, by the computing device, the published first patron data change event and the published second data change event after a period of time.