EAI Practices

PRISM IT provides Enterprise Application Integration ( EAI ) services to ensure successful delivery of consulting services to various fortune 500 organizations by highly experience professionals. We expertise in real-time, near real-time and batch processing mechanism of integrating various application and systems across the enterprise

In real-time processing, small groups of transactions are processed on  demand. Instead of a single run, there is data that arrives continuously  to be processed by a program. The load of processing data is spread  across the day when transactions occur. The advantage of real-time  processing is that it increases access to data, runs with fewer  resources, and improves uptime. With continuous integration of data, you  have knowledge of your business as transactions occur. With small  groups of transactions to process, it can be run periodically during the  day without impacting interactive users. If an error occurs, it can be  handled immediately by staff who are already on site, and the system has  a larger window of time to recover. It is more difficult to design  real-time processing and it includes some additional overhead, so not  every system should be architected as real-time

Near real-time or event driven message based architecture are very common in any mature organization. EDA or Event Driven Architecture is a combination of synchronous and asynchronous way to represent data in a timely manner either using HTTP or TCP as a protocol

The state of change of data can be represent as Events. Event-Driven architectures often being design on top of message-driven architectures. The architectural pattern applied by the systems that transmit events among loosely coupled software components and services is an event-driven solution. It typically consists of event emitters publishers, event consumers, and event channels. Publishers have the responsibility to detect, gather, and transfer events. An Event Publisher does not know the consumers of the event, it does not even know if a consumer exists, and in case it exists, it does not know how the event is used or further processed. The consumer have the responsibility to filter, transform and forward the event to another component or it might provide a self-contained reaction to such event. Event channels are conduits in which events are transmitted from event publishers to event consumers. The physical implementation of event channels can be based on traditional components such as message-oriented middle-ware or point-to-point communication or broadcasting messages over a topic

Building applications and systems around an event-driven architecture allows these applications and systems to be constructed in a manner that facilitates more responsiveness, because event-driven systems are, by design, more normalized to unpredictable and asynchronous environments. Event-driven architecture can complement service-oriented architecture (SOA) because services can be activated by triggers fired on incoming events. 

SOA 2.0 evolves the implications SOA and EDA architectures provide to a richer, more robust level by leveraging previously unknown causal relationships to form a new event pattern. This new business intelligence pattern triggers further autonomous human or automated processing that adds exponential value to the enterprise by injecting value-added information into the recognized pattern which could not have been achieved previously

Jobs that can run without end user interaction, or can be scheduled to run as resources permit, are called batch jobs. Batch processing is for those frequently used programs that can be executed with minimal human interaction

Regardless the size of the enterprise, nightly batch processing is a very common and widely used integration mechanism which transfers transactional and/or non-transactional data from one to many systems or applications to many to one systems or applications