Flat file Integration
Standard Format for each of the document will be defined.
Standard Mapping between the document and the receiving sending application must be in place.
Whichever applications takes in or sends out this document must have developed a interface like API or a function to interact.
All such documents are placed in a defined repository where the APIs or equivalent will access and process.
Pros:
- Flat Files integrations are cheaper solution in terms of cost if the source and target systems are fixed.
- Low Cost Solution
- Quick to develop
Cons:
- Needs FTP Infrastructure and SQL Loader licenses and Programming skills
- When the new systems are introduced into integration, Integration of new systems skilled resources required.
- Data orchestration between the systems is not possible. All are point -to- point integrations
- No single point of monitoring for all integrations.
- Dependency on the experts of interacting application
- Poor Error Handling
- Scalability issues
- Less ease of use
- Difficult to maintain
- NetChange data becomes quite critical
Best to adopt when:
- budget is limited
- Standard formats of data exchange are in place
- Field Mapping and Logic is not going to change much
- No extension plans
- Data volumes are not high
- timelines are tight
- Expertize for developing and maintaining is abundantly available in the Customer organization
No comments:
Post a Comment