Foojay Today

Journeys in Java, Level 7: Externalize Microservice Configuration

January 30, 2023


Our decided next step for this project takes us in a new direction by adding externalized configuration for our applications.

We already saw how to do something similar with MongoDB database credentials in Docker Compose to access a local database container, but what do we do when the database is hosted on public cloud or contains sensitive data?

We probably don’t want to publish our credentials anywhere or even prevent accidental publishing.

This is where solutions such as Spring Cloud Config come into play.

Our Neo4j database free instance is hosted by Neo4j on a public cloud, so we can set the credentials in an external location (such as a local file or other system) use Spring Cloud Config to access those keys and pass them to the approved application.

In this article, we will walk through how to set up a service that hosts the Spring Cloud Config server and how to wire our existing Neo4j microservice (service4) as the config client service to utilize the credentials for accessing Neo4j.

Let’s dive in!


We began this microservices project with minimum functionality explained in the level 1 blog post. In our last post (level6), we added a graph database to our microservices system to take advantage of data relationships between books, authors, and reviews.

With today’s next step, we will add a new service to host managing the credentials and incorporate pulling credentials from there into our Neo4j service.

Here is the updated architecture:

microservices level7

We haven’t incorporated our Neo4j service to the rest of our Docker Compose system of services because I felt that the configuration was the next logical step to avoid hard-coding database credentials in our application or compose file. The eventual goal is to add the MongoDB database credentials to Spring Cloud Config, as well, and remove all hard-coded credentials from the applications and Docker Compose.

Until then, our intermediary step is to add the config-server service and plug that into our existing service4 that connects to Neo4j.

Spring Cloud Config

The project overview for Spring Cloud Config has a good explanation of design and usage, but I’ll briefly put it into my own words here.

Spring Cloud Config gives us a way to externalize configuration, so that individual services can access only the properties they need to operate. Through a config server, we can set up varying environments so that credentials are organized and managed without manipulating values for testing. The project (by default) is set to use Git for the version-controlled properties files, but it can be set up to use other tools or implementations for managing environments and values.

Without further ado, let’s start coding!

Applications - Spring Cloud Config Server

As we have done with our previous services, we will use the Spring Initializr at to set up the outline for our config server application.

On the form, we can leave Project, Language, and Spring Boot version fields defaulted. Under the Project Metadata section, I updated the group name for my personal projects, but you are welcome to leave it defaulted. I named the artifact config-server, though naming is up to you, as long as we map it properly where needed. All other fields in this section can remain as they are. Under the Dependencies section, we need only Config Server (Spring Cloud Config). Finally, the project template is complete, and we can click the Generate button at the bottom to download the project.

springio configserver

Figure 1. Spring Initializr project

Generating will download the project as a zip, so we can unzip it and move it to our project folder with the other services. Open the project in your favorite IDE and let’s get coding!

The pom.xml contains the dependencies and software versions we set up on the Spring Initializr, so we can move to the file in the src/main/resources folder.


Just like with our other services, we need to specify a port number for this application to use so that its traffic doesn’t conflict with our other services. The default port for Spring Cloud Config server is 8888, so we will use that. Next, we will use git to version-track our local configuration file, so we need to specify the folder (or public repository URL, if we had that instead) as the value for the second property.

On to the project code!

Config Server - project code

There is very little we need to add, since we are using the default setup. We don’t have any big customizations or features required for now. So, there is only one small annotation we need to add to the class.

public class ConfigServerApplication {
	public static void main(String[] args) {, args);

The @EnableConfigServer annotation notifies Spring that this application needs to operate as the config server.

Now we need to add our configuration file that will contain the database credentials!

Storing config values

We need an externalized place for our configuration values to reside, i.e. a file with our database credentials for config server to retrieve. Most of the tutorials you find on Spring Cloud Config recommend starting with a local config folder containing either a .properties or .yaml file. I went with the YAML file for this project.

A sample of the file is in the microservices-java-config folder of the Github project.

    uri: <insert Neo4j URI here>
    database: <insert Neo4j database here>
      username: <insert Neo4j username here>
      password: <insert Neo4j password here>

We will need to fill in the values for our Neo4j AuraDB free instance in place of the dummy URL, database, username, and password shown above. Note: Database should be neo4j, unless you have specifically used commands to change the default. Then, we need to save the file and check it into to git by running the next statements from the command line.

microservices-java-config % git init
microservices-java-config % git add
microservices-java-config % git commit -am "Initial commit"

Let’s test our config server application!

Test Config Server

Start the application from your IDE or command line. To test, we need to figure out the correct URL to ping. First, we are running the application locally and set the port to 8888, so the first part of the URL is localhost:8888. The rest of the URL is what confused me in most of the tutorials, but once you know what the application is looking for, it isn’t as intimidating.

Many tutorials use the /{application}/{profile} notation. The /{application} piece references the name you give your client application. This is an arbitrary name, except that your config file (in our case, yaml) needs to have the same name. Config file naming follows the pattern {application}-{profile}. If you do not specify a -{profile} (e.g. development, production) on the config file name, it uses the default profile.

Since our config file is named neo4j-client.yaml, our application name is neo4j-client. We do not specify a profile on our config file name, so it will use the default. This means the /{profile} piece of the URL is default.

Our full URL for testing is then localhost:8888/neo4j-client/default!

config server test

Figure 2. Neo4j config results

Next, we need to plug our client service (service4) in to use the config server we just set up.

Service4 - modifications

To start, we need to add a dependency to service4 for the Spring Cloud Config client. Open the pom.xml and add the following items:

	//java version property
	//other dependencies

On the third line of the above code, we add a property for the Spring Cloud Version. This allows us to source this value anywhere it’s needed in the pom. In the dependencies section, we need to add the config client dependency (seventh line), making this application a client that will use the config server. Last, but not least, we add a dependency management section (line twelve) to handle versioning of Spring Cloud.

Now we need to update the application properties in the src/main/resources folder.


We leave the port property alone, but we can remove the database credential properties because those are being stored in the config server now. The next two properties specify the application name and where the config server is running. Remember that our application name and the name of our config file MUST match. So, that means our needs to be neo4j-client, as our config file name is neo4j-client.yaml. This is also the name that would be referenced between microservices or for service discovery, though we haven’t delved into that part of microservices yet. 😉 Our config server is running locally and on the default config server port, so the value of the last property should look familiar.

This actually wraps up all of our changes to the Neo4j service! We don’t need to change anything in the class because all of our config values are injected as part of the environment, so everything operates in the background.

Let’s test it!

Put it to the test

As always, we will kick things off from the bottom to the top. First, ensure the Neo4j AuraDB instance is still running. *Note:* AuraDB free tier pauses automatically after 3 days. You can resume with the play icon on the instance.

Next, we need to start our config-server application, either through the IDE or command line. Once that is running, we can start the service4 application through the IDE or command line. Time to test the application using the following commands.

  1. Test config server is working: open a browser and go to localhost:8888/neo4j-client/default or go to command line with curl localhost:8888/neo4j-client/default.
  2. Test service4 is live: open a browser and go to localhost:8083/neo or go to command line with curl localhost:8083/neo.
  3. Test backend reviews api: open a browser and go to localhost:8083/neo/reviews or go to command line with curl localhost:8083/neo/reviews.
  4. Test reviews api for a certain book: open a browser and go to localhost:8083/neo/reviews/178186 or go to command line with curl localhost:8083/neo/178186.

And here is the resulting output from reviews api results!

microservices lvl7 results

Figure 3. Find 1000 reviews

microservices lvl7 results book

Figure 4. Find reviews by book

Wrapping up!

Today, we incorporated the Spring Cloud Config project to manage and provide database credentials to our Neo4j microservice.

We created a new service to host the config server and set up an external YAML file containing our database credentials.

We saw how to test those pieces and verify the config server was working before moving on to plug in our service4 application as the client to use the values provided by the config server.

The client service didn’t require too many code changes to do this, and then we tested those components (config server, config file, Neo4j microservice) together to ensure we could access our review data as expected.

There are still a few things that we can do on this topic.

  • It would be nice to add our MongoDB credentials to the Spring Cloud Config server, as well, and remove the hard-coded values from Docker Compose.
  • We also need to incorporate the Neo4j microservice and config service with the rest of our group in Docker Compose.

Happy coding!



Related Articles

View All


Comments (0)

Your email address will not be published. Required fields are marked *

Highlight your code snippets using [code lang="language name"] shortcode. Just insert your code between opening and closing tag: [code lang="java"] code [/code]. Or specify another language.

Save my name, email, and website in this browser for the next time I comment.

Subscribe to foojay updates:
Copied to the clipboard