EAI / ESB
We build an environment to efficiently manage business by stably linking complex and diverse
information systems in various industries such as public, financial, manufacturing, and telecommunications.
EAI
EAI is a concept that refers to an attempt to increase work efficiency by integrating different applications operated by companies such as
data warehouse (DW) or enterprise resource management (ERP) within the organization.
It means plans, methods, tools, etc. aimed at modernizing, integrating, and coordinating computer applications within the enterprise.
EAI Introduction effect
EAI Disadvantages before introduction
System independence cannot be guaranteed due to point-to-point connection
Excessive modification occurs when system changes
Difficult to change the process (Ripple Effect)
Business logic cannot be reused
Lack of information flow between systems
EAI Advantages
Increasing reuse rate by oriented simple architecture
Easy to expand when introducing new applications
Increased development convenience
Increased maintenance convenience
Increased convenience of error detection, logging, and recovery
As EAI is the center, and multiple systems to be interfaced through EAI, each legacy system can interwork with multiple types of legacy systems
with a single interface type for EAI. In addition, this centralized EAI features the characteristics of middleware,
It provides data conversion, role-based processing, and transaction integrity.
ESB
ESB is a middleware that connects and integrates services, applications, and resources within the business
Through this, distributed service components can be easily integrated and linked to enable reliable message communication.
ESB Characteristic
ESB Characteristic
A service infrastructure that supports IT architecture that bundles corporate
information systems around shared and reusable services and components.
Integrated support through standard-based systematically defined interface
Multi-protocol support / BPM support / event-oriented for interworking
with various systems
ESB Component
Adapter-type legacy interworking
component
The ESB should support various standard protocols in the form of adapters, and should be configured in a form that can be easily integrated in an integrated development environment, not a library in the form of a source.
Message conversion and processing
Systems interlocked with ESB should be able to freely convert and process data formats and forms in an integrated development environment.
Control and monitoring
Integrated control and monitoring from the connection status of the adapter to the process status and data should be possible.
Integrated development environment
If development is done through several tools other than the integrated development environment, or if the tool itself is not provided, the development efficiency has to drop sharply, and the integrated development environment is an essential element of the ESB.
Architecture
