DESCRIPTION:
Shares the functionality of registering the system service within a catalogue to be discovered by other services.
Source ISA2 - EIA Action
Syn. Service Catalogue Service
INTEROPERABILITY SALIENCY:
The Service Registration Service ABB is salient for interoperability because it enables the registration of services in a catalogue with commonly agreed descriptions as stated in the EIF recommendation n°44: "Put in place catalogues of public services, public data, and interoperability solutions and use common models for describing them."
EXAMPLES:
The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB):
Apache ZooKeeper
Apache ZooKeeper is an effort to develop and maintain an open-source server which enables highly reliable distributed coordination.
ZooKeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these kinds of services are used in some form or another by distributed applications. Each time they are implemented there is a lot of work that goes into fixing the bugs and race conditions that are inevitable. Because of the difficulty of implementing these kinds of services, applications initially usually skimp on them, which make them brittle in the presence of change and difficult to manage. Even when done correctly, different implementations of these services lead to management complexity when the applications are deployed.
ZooKeeper aims at distilling the essence of these different services into a very simple interface to a centralized coordination service. The service itself is distributed and highly reliable. Consensus, group management, and presence protocols will be implemented by the service so that the applications do not need to implement them on their own. Application specific uses of these will consist of a mixture of specific components of Zoo Keeper and application specific conventions. ZooKeeper Recipes shows how this simple service can be used to build much more powerful abstractions.
Apache have Java and C interfaces to Zoo Keeper for the applications themselves. A variety of client bindings is available for a number of languages including Python, Ruby and Go.
https://cwiki.apache.org/confluence/display/ZOOKEEPER/Index
|
|
| ID | ABB189 |
| dct:type | eira:ServiceRegistrationService |
| dct:publisher | |
| dct:modified | |
| eira:status | [ Exists | Development planned ] |
| eira:reusability | [ Excellent (90-100%) | Very good (70-89,9%) | Fair (50-74,9%) | Poor (0-49,9%) ] |
| eira:actual_use | [ Currently used | Used planned | No ] |
| difi:namespace | eira |
| difi:name_no | |
| difi:description_no | |
| difi:name_en | Service Registration Service [ns:eira] |
| difi:description_en | DESCRIPTION:
Shares the functionality of registering the system service within a catalogue to be discovered by other services.
Source ISA2 - EIA Action
Syn. Service Catalogue Service
INTEROPERABILITY SALIENCY:
The Service Registration Service ABB is salient for interoperability because it enables the registration of services in a catalogue with commonly agreed descriptions as stated in the EIF recommendation n°44: "Put in place catalogues of public services, public data, and interoperability solutions and use common models for describing them."
EXAMPLES:
The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB):
Apache ZooKeeper
Apache ZooKeeper is an effort to develop and maintain an open-source server which enables highly reliable distributed coordination.
ZooKeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these kinds of services are used in some form or another by distributed applications. Each time they are implemented there is a lot of work that goes into fixing the bugs and race conditions that are inevitable. Because of the difficulty of implementing these kinds of services, applications initially usually skimp on them, which make them brittle in the presence of change and difficult to manage. Even when done correctly, different implementations of these services lead to management complexity when the applications are deployed.
ZooKeeper aims at distilling the essence of these different services into a very simple interface to a centralized coordination service. The service itself is distributed and highly reliable. Consensus, group management, and presence protocols will be implemented by the service so that the applications do not need to implement them on their own. Application specific uses of these will consist of a mixture of specific components of Zoo Keeper and application specific conventions. ZooKeeper Recipes shows how this simple service can be used to build much more powerful abstractions.
Apache have Java and C interfaces to Zoo Keeper for the applications themselves. A variety of client bindings is available for a number of languages including Python, Ruby and Go.
https://cwiki.apache.org/confluence/display/ZOOKEEPER/Index
|
| difi:language | en |
| label | ${name} [lang:${property:difi:language}] |
| difi:abstractionLevel | abb |