Storing Service Metadata: A Service Registry Use Case

EDITOR’S NOTE: Rackspace Service Registry is no longer available.

Late last year, we launched the Rackspace Service Registry into preview. The tool helps developers make their applications highly available through exposing the building blocks for automation and centralized configuration storage. It is one of the first Rackspace services focused on helping our customers run and automate their application versus their infrastructure.

There are several use cases for Service Registry. On the Rackspace DevOps Blog, I dig deeper into storing service metadata in Service Registry.

Each service object in the Service Registry has a metadata field that stores arbitrary string key and value pairs. Some of the common values you can store in this field include application version, the region and data center where the service is running, the timestamp of when a service started, JMX port for Java services and a stats port. That information can be used to display a list of services with on an internal dashboard; for client side filtering based on some metadata attribute; and for finding services which are out of date.

Head over to the DevOps Blog to read about this use case in more detail.

In upcoming posts we’ll look at more advanced use cases, including using service registry for middle-tier load balancing and using events feed as one of the information sources for your automation system.

Service Registry is currently in closed preview and is available free of charge. If you want access to the preview, you can request it by filling out this survey.

Rack Blogger is our catchall blog byline, subbed in when a Racker author moves on, or used when we publish a guest post. You can email Rack Blogger at


Please enter your comment!
Please enter your name here