concept Git in category microservice

appears as: Git
Spring Microservices in Action

This is an excerpt from Manning's book Spring Microservices in Action.

  • Git— Git (https://git-scm.com/) is an open source version control system that allows you to manage and track changes to any type of text file. Spring Cloud Config can integrate with a Git-backed repository and read the application’s configuration data out of the repository.
  • Table 3.1. Open source projects for implementing a configuration management system (view table figure)

    Project Name

    Description

    Characteristics

    Etcd Open source project written in Go. Used for service discovery and key-value management. Uses the raft (https://raft.github.io/) protocol for its distributed computing model. Very fast and scalable Distributable Command-line driven Easy to use and setup
    Eureka Written by Netflix. Extremely battle-tested. Used for both service discovery and key-value management. Distribute key-value store. Flexible; takes effort to set up Offers dynamic client refresh out of the box
    Consul Written by Hashicorp. Similar to Etcd and Eureka in features, but uses a different algorithm for its distributed computing model (SWIM protocol; https://www.cs.cornell.edu/~asdas/research/dsn02-swim.pdf). Fast Offers native service discovery with the option to integrate directly with DNS Doesn’t offer client dynamic refresh right out of the box
    ZooKeeper An Apache project that offers distributed locking capabilities. Often used as a configuration management solution for accessing key-value data. Oldest, most battle-tested of the solutions The most complex to use Can be used for configuration management, but should be considered only if you’re already using ZooKeeper in other pieces of your architecture
    Spring Cloud configuration server An open source project that offers a general configuration management solution with different back ends. It can integrate with Git, Eureka, and Consul as a back end. Non-distributed key/value store Offers tight integration for Spring and non-Spring services Can use multiple back ends for storying configuration data including a shared filesystem, Eureka, Consul, and Git

    By using Git you can get all the benefits of putting your configuration management properties under source control and provide an easy mechanism to integrate the deployment of your property configuration files in your build and deployment pipeline.

    To use Git, you’d swap out the filesystem back configuration in the configuration service’s bootstrap.yml file with the following listing’s configuration.