Friday, July 15, 2011

Non Functional Requirements of Integration Projects (EAI and B2B)

  • No Data loss in any case. Data should be recoverable in integration layer.
  • Recovery should be automatic in majority of the cases in case of integration layer failure.
  • Replay of messages must be possible in all case of failure.
  • End systems to be integrated, should be decoupled in time, space and semantic.
  • Contingency path/scenarios (if deployment fails or integration is need to be rolled back after successful run in production after a while) must be defined and rehearsed.
  • There must be clear separation between Integration and Services.
  • Underlying integration service failure (like audit, logging, notification, error handling, etc) must not affect integration as well as enterprise services.
  • Audit, error notification, error repository should be deployed on separate servers/infrastructure from business services and integration.

No comments:

Post a Comment