Document event brokering and audit system
A system for managing business to business communications may include an event generation unit configured to create a first event based on receiving a purchase order from a client. The system may also include an event detection unit in communication with the event generation unit, the event detection unit configured to detect the first event. The system may also include an action unit in communication with the event generation unit. The action unit may be configured to determine a first action to perform based on the detection of the first event, and perform the first action. The event generation unit may be further configured to create a second event based on the performance of the first action.
1. A method for improving processing times, comprising:
dispatching events to event listeners by using an event broker in a compute layer;
processing an event of the events using an event listener in the compute layer;
storing the events in a sharded database cluster by the event broker in a persistence layer;
assigning shard chunks on each shard node of a sharded database;
adding new shards to the sharded database, in response to the event broker generating new events based on a configuration parameter with an increased listener hash range;
rebalancing of instances of a component listener based on health collections of the components and an allocation of a listener hash range for each instance of the component listener;
configuring a number of dispatcher threads in an event broker listener;
running multiple event listeners in parallel for the event such that the instance of the event listener receives the event;
sending database operations in a batch to a data layer, wherein an insert and multiple updates are incorporated into a single insert command to the sharded database;
storing the event, a command and an audit together in bulk; and
identifying electronic documents with higher priority based on metadata structures, wherein the electronic documents with the higher priority are processed faster.
2. The method of claim 1 , wherein the dispatching events is at least one of in memory in response to a component running on a same virtual machine as an event producer and the component listener has a free slot to accept the event, or via a query system wherein a virtual machine queries for the event, in response to the event listener being able to process the event.
3. The method of claim 1 , wherein the dispatching events is via a query system using a listener hash to reduce contention at a database level.
4. The method of claim 1 , further comprising an event bus performing a query dispatch for new computing resources to come online, in response to the event listener being slow.
5. The method of claim 1 , further comprising assigning to the event at least one of a partition or a hash number associated with the component listener.
6. The method of claim 1 , further comprising processing the event by one instance of the event listener.
7. The method of claim 1 , further comprising re-balancing instances of the component listener such that the component listener is assigned to process a range of listener hashes.
8. The method of claim 1 , further comprising grouping the events to provide groupings in different parts of an event bus.
9. The method of claim 1 , further comprising running multiple listeners in parallel such that one instance of the event listener receives the event.
10. The method of claim 1 , wherein the events include at least one of metadata, a state of the electronic document, identifying a format of the electronic document, enriching the electronic document, a signature verification, identifying content within the electronic document, decrypting the electronic document, an organization change or a system notification.
11. The method of claim 1 , wherein the events include a listener hash that is used as a shard key.
12. The method of claim 1 , wherein an event bus allows visibility of at least one of the components that are going to receive the event when the components are ready to process the event, the components that are actively processing the event, the components finished processing the event, real-time processing metrics, events assigned but not dispatched, the component listener with events assigned but backlogged, or metrics into internal queues, threads and processing times.
13. The method of claim 1 , further comprising an electronic document audit tracking subsystem on top of an event bus, wherein the electronic document audit tracking subsystem moves events related to transacting the electronic document into another set of document meta-data collections.