CRecordMicroServiceInstance

This data record contains the information about a single microservice instance.

This message belongs to the microservice registry API.

{
  "id": "116d6164-0769-4774-92d6-258b0807163a",
  "name": "MICRO_SERVICE_INSTANCE",
  "description": "A microservice instance.",
  "slots": [
    {
      "key": "1",
      "name": "MICRO_SERVICE_ID",
      "direction": "REQUEST",
      "mandatory": "true",
      "type": "ID",
      "description": "The microservice ID."
    },
    {
      "key": "2",
      "name": "MICRO_SERVICE_INSTANCE_ID",
      "direction": "REQUEST",
      "mandatory": "true",
      "type": "ID",
      "description": "The microservice instance ID."
    },
    {
      "key": "3",
      "name": "MICRO_SERVICE_ADDRESS",
      "direction": "REQUEST",
      "mandatory": "true",
      "type": "TARGET_ADDRESS",
      "description": "The microservice target address."
    },
    {
      "key": "4",
      "name": "TIME_ADDED",
      "direction": "REQUEST",
      "mandatory": "true",
      "type": "ZONED_DATE_TIME",
      "description": "The time the microservice instance has been added."
    }
  ]
}

Message Arguments

Key Name Direction Mandatory Type Description
1 MICRO_SERVICE_ID REQUEST true ID The microservice ID.
2 MICRO_SERVICE_INSTANCE_ID REQUEST true ID The microservice instance ID.
3 MICRO_SERVICE_ADDRESS REQUEST true TARGET_ADDRESS The microservice target address.
4 TIME_ADDED REQUEST true ZONED_DATE_TIME The time the microservice instance has been added.

Usage

Example of use: see here.

Record Usage

In nyssr.net, we typically don't exchange interfaces between projects. Instead, we use platform-independent Records to describe message formats.

One or more descriptions of these Records are stored in the JSON or XML format as record.json or record.xml within a directory. The Record Generator, an included Swing tool, generates helper classes from these files. These classes can then be used to type-safely write or read messages.

See also