Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

SpringOne Replay: Implementing and Extending Config Server

DZone's Guide to

SpringOne Replay: Implementing and Extending Config Server

This overview of Spring Cloud Config Server touches on source control, security, and extensibility, including how to give it capabilities akin to CloudFoundry services.

· Cloud Zone ·
Free Resource

See why enterprise app developers love Cloud Foundry. Download the 2018 User Survey for a snapshot of Cloud Foundry users’ deployments and productivity.

Spring Cloud Config Server is a great tool for getting your application configuration under source control. We’ll start with a quick overview of Spring’s environment and properties and how Config Server enhances those — while keeping the same model.

Next, we’ll discuss what concerns you need to take into account when rolling out Config Server — like security, encryption, and location of your repositories (if using Git).

Finally, we’ll discuss Config Server’s extensibility, particularly dealing with security (since Config Server serves up properties decrypted) and even going so far as adding ‘Filtering’ to allow for capabilities akin to CloudFoundry ‘Services’ for making shared configs that are available across many applications, even accounting for how you might test those extensions.

Recorded at SpringOne Platform 2016.

Speaker: Clint Checketts, Domo.com

Slides: http://www.slideshare.net/SpringCentral/implementing-config-server-and-extending-it

Cloud Foundry saves app developers $100K and 10 weeks on average per development cycle. Download the 2018 User Survey for a snapshot of Cloud Foundry users’ deployments and productivity. Find out what people love about the industry standard cloud application platform.

Topics:
spring cloud ,config server ,source control ,cloud

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}