Answers: <p>According to <a href="https://landscape.cncf.io/images/landscape.png" rel="nofollow noreferrer">the Cloud Native Landscape</a>, you are looking for a <code>Coordination &amp; Service Discovery</code>:</p>
  
  <p><a href="https://i.sstatic.net/KPSba.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/KPSba.png" alt="enter image description here"></a></p>
  
  <p><a href="https://etcd.io/" rel="nofollow noreferrer">https://etcd.io/</a></p>
  
  <blockquote>
    <p>A distributed, reliable key-value store for the most critical data of
    a distributed system</p>
  </blockquote>
  
  <p><a href="https://github.com/Netflix/eureka" rel="nofollow noreferrer">https://github.com/Netflix/eureka</a></p>
  
  <blockquote>
    <p>Eureka is a REST (Representational State Transfer) based service that
    is primarily used in the AWS cloud for locating services for the
    purpose of load balancing and failover of middle-tier servers.</p>
  </blockquote>
  
  <p><a href="https://github.com/alibaba/nacos" rel="nofollow noreferrer">https://github.com/alibaba/nacos</a></p>
  
  <blockquote>
    <p>Nacos (official site: <a href="http://nacos.io" rel="nofollow noreferrer">http://nacos.io</a>) is an easy-to-use platform
    designed for dynamic service discovery and configuration and service
    management. It helps you to build cloud native applications and
    microservices platform easily.</p>
  </blockquote>
  
Answers: CC BY-SA 4.0
Answers: 2019-08-22T07:42:12.187Z
Answers: thank you very much for the answer. However, my experience with `registry and service discovery` e.g. Netflix Eureka, falls short of my requirements.  There are two major reasons, first, the systems you listed retain information ephemerally i.e. all information is lost following a shutdown. Secondly, asides the application metadata e.g. endpoints, it is important to have knowledge about deployment dates, test dates i.e. the information about the application's lifecycle. Therefore, I was hoping for a solution that aggregates all these disjointed pieces of information.
Answers: SyCode
Answers: CC BY-SA 4.0
Answers: 2019-08-22T14:43:49.883Z
Answers: Maybe Helm could fill the role of providing the deployment dates and other lifecycle things?
Answers: Randy L
Answers: CC BY-SA 4.0
Answers: 2019-08-22T16:55:01.400Z
Answers: @theOther can you briefly explain? I am not conversant with helm, a quick look at the documentation (https://helm.sh/docs/using_helm/#quickstart) gives me no clues.
Answers: SyCode
Answers: CC BY-SA 4.0
Answers: 2019-08-21T21:53:24.017Z
Answers: 2019-08-21T21:53:24.017Z
Answers: 030
Body: <p>I was wondering how information on deployed applications are kept in real, production environments (yeah, I am a novice) . For example, in a microservices based set up, if  5 microservices-based  applications were deployed in production environments. Let's say each of those had 4 - 6 instances each, are there special software for keeping record of these applications? I know the records can be easily written into a database but I can imagine some better solutions out there. </p>
  
Tags: <deployment><continuous-deployment><microservices>
Title: Microservices Deployment Manager
UserDisplayName: SyCode
ThreadText: # Microservices Deployment Manager
  
  (Asked by: username_0 on 2019-08-21)
  
  I was wondering how information on deployed applications are kept in real, production environments (yeah, I am a novice) . For example, in a microservices based set up, if 5 microservices-based applications were deployed in production environments. Let's say each of those had 4 - 6 instances each, are there special software for keeping record of these applications? I know the records can be easily written into a database but I can imagine some better solutions out there.
  
  **Tags:** deployment, continuous-deployment, microservices
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-08-21. Score: 1
  
  According to [the Cloud Native Landscape](https://landscape.cncf.io/images/landscape.png), you are looking for a `Coordination & Service Discovery`:
  
  [![enter image description here](https://i.sstatic.net/KPSba.png)](https://i.sstatic.net/KPSba.png)
  
  <https://etcd.io/>
  
  > A distributed, reliable key-value store for the most critical data of
  > a distributed system
  
  <https://github.com/Netflix/eureka>
  
  > Eureka is a REST (Representational State Transfer) based service that
  > is primarily used in the AWS cloud for locating services for the
  > purpose of load balancing and failover of middle-tier servers.
  
  <https://github.com/alibaba/nacos>
  
  > Nacos (official site: <http://nacos.io>) is an easy-to-use platform
  > designed for dynamic service discovery and configuration and service
  > management. It helps you to build cloud native applications and
  > microservices platform easily.
  
  > **Comments:**
  > **username_0**: thank you very much for the answer. However, my experience with `registry and service discovery` e.g. Netflix Eureka, falls short of my requirements.  There are two major reasons, first, the systems you listed retain information ephemerally i.e. all information is lost following a shutdown. Secondly, asides the application metadata e.g. endpoints, it is important to have knowledge about deployment dates, test dates i.e. the information about the application's lifecycle. Therefore, I was hoping for a solution that aggregates all these disjointed pieces of information.  
  > **username_2**: Maybe Helm could fill the role of providing the deployment dates and other lifecycle things?  
  > **username_0**: @theOther can you briefly explain? I am not conversant with helm, a quick look at the documentation (https://helm.sh/docs/using_helm/#quickstart) gives me no clues.  
  
  ---
  
  