Open Integration Standards

Components must be accessible through open, non-proprietary standards (with a preference for HTTP & in-particular REST)

Rationale

Proprietary standards and applications inhibit open integration and extensibility. In order to create a platform for innovation we need to embrace open communication standards. Embracing the best practices of the web gives not only the desired openness but also the scalability.

Implications

  • Products that require complex integration technologies must be wrapped with an isolation layer or, ultimately, replaced with something that does not rely on closed communication protocols.
  • Services will be required to provide the ability to discover all capabilities that they offer through their API
  • Standards that are derived from working software and not just working groups are preferred. Battle tested standards used by several organisations tend to be more useful than over-engineerd hot air. Most succesfull standards tend to be the ones that are adopted by Open Source communities.

results matching ""

    No results matching ""