Home > Standards > Integration Standards

What are Integration Standards?

Key Points

  • integration Standards are rules establishing how request and responses are described and given.
  • Using standards makes integration service can be shared by more than just the project or person that created the data.
  • Standards are useful for integrating data from multiple resources. If the various sources agreed upon a standard to begin with, this saves time reconciling any differences.

Integration is the act of bringing together components of various system that functions as one. In an IT context, integration refers to the end result of a process that aims to stitch together different, often disparate, subsystems so that the data contained in each becomes part of a larger, more comprehensive system that, ideally, quickly and easily shares data when needed

Why do we need Integration Standards?

Using standards makes using things easier.Traditional system development approach for e-governance solution will create chaotic situation when different vendor usage different method to intgrate with one another and it becomes difficult to maintain interoperability among the system. Hence it is necessary to define a standard for integration that facilitate software development, maintenance and reuse.

Why Point to Point Integration Isn't Good Enough

When used with small infrastructures, where only two or three systems must be integrated, this model can work quite well, providing a lightweight integration solution tailor-made to the needs of the infrastructure. However, as additional components are added to an infrastructure, the number of point-to-point connections required to create a comprehensive integration architecture begins to increase exponentially.

A three-component infrastructure requires only three point-to-point connections to be considered fully integrated. By comparison, the addition of just two more components increases this number to 10 connectors. This is already approaching an unmanageable level of complexity, and once an infrastructure includes 8 or 9 component systems, and the number of connections jumps into the 30s, point-to-point integration is no longer a viable option.

Remember that each of these connectors must be separately developed and maintained across system version changes, scalability changes, and more (or, in some cases, even purchased at high cost from a vendor), and the unsuitability of point-to-point integration for complex enterprise scenarios becomes painfully clear.

Benefits of Integration

  • Less time spent on development
  • Easy to extend standard integration content
  • Standard integrations can be used as templates
  • Content became available on the fly

E-Governance Point of View

Various e-governance project Needed some common features that they often time developed again and again for each system . If these system could be integrated with one another to share there data and services to other system then a viable time of development may be saved. But this could not be done randomly. there sould be some rules and defination for integration. Otherwise the whole scenario might get cheotic.That is why integration standard is needed