Role of Systematic Reuse in Enterprise Integration
- allows the team to evolve consistent set of data interfaces across integration efforts – if multiple systems need to integrate with yours, can you define a generic data model for your domain-specific concepts? This could be file layout(s), service interface schemas, or platform specific APIs
- enables common interfaces for domain specific services and business processes
- integration points often need cross-cutting concerns such as logging, transaction management, exception handling, etc. that can be reused
- reusable utilities can help with support and testing tools – for instance, reply failed messages, drain message queues/topics, generate high volume test data, etc.
Question is – are your teams taking advantage of integration points? or is each integration point implementing identical or similar functionality in an inconsistent fashion?
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)