Service governance for distributed systems

1. A method comprising:

placing a service under purview of an automated service governance system by:

initiating release of a service artifact by a continuous integration job;

extracting, by one or more processors and during execution of the continuous integration job, a plurality of service manifest files associated with a web service from the service artifact, the plurality of service manifest files comprising service metadata corresponding to a plurality of service environments, and at least one service manifest file of the plurality of service manifest files corresponds to an individual service environment of the plurality of service environments that comprises:

a development environment associated with the web service;

a quality assurance environment associated with the web service;

a stating environment associated with the web service; and

a production environment associated with the web service;

validating the plurality of service manifest files based on one or more predetermined criteria associated with at least one of:

a service end-point;

a contract uniform resource locator (URL); or

a valid service environment of the web service; and

publishing the plurality of service manifest files in a service registry associated with the automated service governance system by:

determining whether the service registry comprises a service call of the web service;

in response to determining that the service registry comprises the service call, updating the service call in the service registry;

in response to determining that the service registry does not comprise the service call, creating an entry associated with the web service in the service registry; and

passing the plurality of service manifest files in the service registry to a service publish to publish the plurality of service manifest files.

2. The method of claim 1 , wherein:

the service metadata includes at least one of:

a service name of the web service;

a status storing an operation status of the web service;

a timestamp associated with an operation of the web service;

one or more configuration documents associated with the web service; or

a service description language document of the web service.

3. The method of claim 1 , wherein:

the at least one service manifest file of the plurality of service manifest files is written in an Extensible Markup Language (XML).

4. The method of claim 1 , further comprising:

building the service artifact using maven techniques by packaging the plurality of service manifest files.

5. The method of claim 1 , further comprising:

conducting a Java XML binding (JAXB) read of the plurality of service manifest files before validating the plurality of service manifest files.

6. A method comprising:

providing, by one or more processors, a web service in a cloud computing system based on one or more service contract parameters associated with the web service;

generating a service contract file based on the one or more service contract parameters;

placing a service under purview of an automated service governance system by:

initiating release of a service artifact by a continuous integration job, the service artifact comprising the service contract file;

extracting, during execution of the continuous integration job, a plurality of service manifest files associated with the web service from the service contract file, the plurality of service manifest files comprising service metadata corresponding to a plurality of service environments, and at least one service manifest file of the plurality of service manifest files corresponds to an individual service environment of the plurality of service environments that comprises:

a development environment associated with the web service;

a quality assurance environment associated with the web service;

a stating environment associated with the web service; and

a production environment associated with the web service;

validating the plurality of service manifest files based on one or more predetermined criteria associated with at least one of:

a service end-point;

a contract uniform resource locator (URL); or

a valid service environment of the web service; and

publishing the plurality of service manifest files in a service registry associated with the automated service governance system by:

determining whether the service registry comprises a service call of the web service;

in response to determining that the service registry comprises the service call, updating the service call in the service registry; and

in response to determining that the service registry does not comprise the service call, creating an entry associated with the web service in the service registry; and

passing the plurality of service manifest files in the service registry to a service publish to publish the plurality of service manifest files.

7. The method of claim 6 , wherein:

the service metadata includes at least one of:

a service name of the web service;

a status storing an operation status of the web service;

a timestamp associated with an operation of the web service;

one or more configuration documents associated with the web service; or

a service description language document of the web service.

8. The method of claim 6 , wherein:

the service contract file is written in an Extensible Markup Language (XML).

9. One or more non-transitory computer readable media comprising computer-executable instructions that, when executed by a computer, perform acts comprising:

placing a service under purview of an automated service governance system by:

initiating release of a service artifact by a continuous integration job;

extracting, during execution of the continuous integration job, a plurality of service manifest files associated with a web service from the service artifact, the plurality of service manifest files comprising service metadata corresponding to a plurality of service environments, and at least one service manifest file of the plurality of service manifest files corresponds to an individual service environment of the plurality of service environments that comprises:

a development environment associated with the web service;

a quality assurance environment associated with the web service;

a stating environment associated with the web service; and

a production environment associated with the web service;

validating the plurality of service manifest files based on one or more predetermined criteria associated with at least one of:

a service end-point;

a contract uniform resource locator (URL); or

a valid service environment of the web service; and

publishing the plurality of service manifest files in a service registry associated with the automated service governance system by:

determining whether the service registry comprises a service call of the web service;

in response to determining that the service registry comprises the service call, updating the service call in the service registry; and

in response to determining that the service registry does not comprise the service call, creating an entry associated with the web service in the service registry; and

passing the plurality of service manifest files in the service registry to a service publish to publish the plurality of service manifest files.

10. The one or more non-transitory computer readable media of claim 9 , wherein:

the service metadata corresponds to a plurality of service environments and comprises:

at least one of:

a service name of the web service;

a status storing an operation status of the web service;

a timestamp associated with an operation of the web service;

one or more configuration documents associated with the web service; or

a service description language document of the web service.

11. The one or more non-transitory computer readable media of claim 9 , wherein:

the at least one service manifest file is written in an Extensible Markup Language (XML).

12. The method of claim 1 , wherein:

the service registry manages version compatibility between a service consumer and a service provider.

13. The method of claim 1 , wherein:

the service metadata includes at least one of:

a service name of the web service;

a status storing an operation status of the web service;

a timestamp associated with an operation of the web service;

one or more configuration documents associated with the web service; or

a service description language document of the web service;

the at least one service manifest file of the plurality of service manifest files is written in an Extensible Markup Language (XML);

the service registry manages version compatibility between a service consumer and a service provider;

the method further comprises:

building the service artifact using maven techniques by packaging the plurality of service manifest files; and

conducting a Java XML binding (JAXB) read of the plurality of service manifest files before validating the plurality of service manifest files.

14. The method of claim 6 , wherein:

the service registry manages version compatibility between a service consumer and a service provider.

15. The method of claim 6 , wherein:

the service metadata includes at least one of:

a service name of the web service;

a status storing an operation status of the web service;

a timestamp associated with an operation of the web service;

one or more configuration documents associated with the web service; or

a service description language document of the web service;

the service contract file is written in an Extensible Markup Language (XML);

the service registry manages version compatibility between a service consumer and a service provider.

16. The one or more non-transitory computer readable media of claim 9 , wherein:

the service registry manages version compatibility between a service consumer and a service provider.

17. The one or more non-transitory computer readable media of claim 9 , wherein:

the service metadata corresponds to a plurality of service environments and comprises:

at least one of:

a service name of the web service;

a status storing an operation status of the web service;

a timestamp associated with an operation of the web service;

one or more configuration documents associated with the web service; or

a service description language document of the web service;

the at least one service manifest file is written in an Extensible Markup Language (XML); and

the service registry manages version compatibility between a service consumer and a service provider.