SOIL

From Wiki

Jump to: navigation, search

Contents

[edit] SOIL - Service Orientation Infrastructure Library

THIS IS YET A DRAFT OF AN INDIVIDUAL

Service Orientation brings it's own set of considerations and challenges and uses specific processes.

Inspired by ITIL - the Information Technology Infrastructure Library - it makes sense to maintain a similar library of best practices and conventions to apply these best practices across different environments, customers, industries.

[edit] Conventions

[edit] Terminology

Specifies terms used in the context of an infrastructure containing service oriented components, as they are used within the context of this library. Prominent terms include Service, Provider, and Consumer.

[edit] Overview

The library is divided into different section.

  • section 'infrastructure' specific to the interface between service oriented components and the underlying infrastructure
  • section 'common components' specific to components specific to a service oriented environments, that are commonly found in such an environment
  • everything else specific to service orientation is collected in a third section 'Core'
  • A forth and fifth section is specific to the challenges of maturity and implementation related to the library

[edit] Reuse

The library reuses methodologies recognized by other industry best practices, i.e. the use of a maturity model.

This is done to facilitate the benefits these externally developed methodologies can deliver, also to increase the recognition of the reader, and ultimately to ease the integration and coexistence between this library and other libraries.

[edit] Focus

The library focuses on infrastructure best practices specific to service orientation.

Related best practices and content of other libraries are not duplicated, and no dependencies injected.

This allows these practices to develop independent of other libraries, and allows an implementation without requiring to follow best practices in areas covered by other libraries.

The library has an culturally and geographically universal focus. The language used as a lingua franka is the english language in the flavour of the united states of america.

[edit] Sections

[edit] Section 1 - Infrastructure

  • Orchestration
  • Configuration management
  • Capacity management

[edit] Section 2 - Common Components

  • Service Gateway
  • Service Directory
  • Service Repository
  • Service Traffic

[edit] Section 3 - Core

  • Service Contract management
  • Service Location management
  • Service Dependency management
  • Service Automation
  • Service Security
  • Community Process

[edit] Section 4 - Maturity

Organizations and communities facilitating service orientation develop their use and capabilities of service orientation between different levels.

This library describes some commonly found levels of service orientation maturity and how they distinguish themselves from each other.

[edit] Section 5 - Implementation

The implementation of any of the best practices and conventions from this library is itself described as a best practice, to allow the reader to avoid pitfalls, and benefit from the experience condensed in this section.

The implementation guidance described in this section is neither comprehensive nor mandatory. The reader is encouraged to benefit and to contribute.

Personal tools