Use of the client libraries

Easily access configuration data stored in ConfigSeeder® directly from your application:

• Add the client library to your project
• Configure access to ConfigSeeder®
• Provide an API Key

With the next start, your application will receive its configuration from ConfigSeeder®.

Benefits of using the ConfigSeeder® client libraries.

The OS Connector and Kubernetes Connector provide configuration data to an application with low coupling to ConfigSeeder®. With the use of a client library, there is higher coupling, but there are also benefits:

• Your application has access to the configuration under control. There are no dependencies on other infrastructure.
• Your application can optionally receive configuration updates during runtime
• When using the Kubernetes Connector or OS Connector, your configuration data is replicated into a ConfigMap, Secret, or File. This is not the case with the client libraries.

Available client libraries

Java

Depending on the exact use case, there are different client libraries for java integration:

Variant	Description
Java	Use this client library if your application is not based on Spring or Eclipse Microprofile.
Spring	Use the Spring client library if you develop an application based on Spring or SpringBoot. (The library implements a property source that integrates flawlessly into the spring concepts)
Eclipse Microprofile	Use this client library if you develop an application based on Eclipse Microprofile. (The library implements a config source that integrates flawlessly into the Eclipse Microprofile concepts)
Maven	Use the Maven plugin if you need to access configuration data during a Maven build.

Golang

Use our go client if you need to access configuration data in your golang based application.

Get the client libraries

The ConfigSeeder® client libraries are available on our download site.