Cookies improve the way our website works, by using this website you are agreeing to our use of cookies. For more information see our privacy policy. OK

CRecordMicroService

This data record describes a microservice.

It serves as a pure data record.

The class that corresponds to this data is the CMicroServiceDescription. 

{
  "id": "62e0f5e4-4410-4308-ae2d-f69e6ac05481",
  "name": "MICRO_SERVICE",
  "description": "A microservice.",
  "slots": [
    {
      "key": "1",
      "name": "ID",
      "direction": "REQUEST",
      "mandatory": "true",
      "type": "ID",
      "description": "The ID of the microservice."
    },
    {
      "key": "2",
      "name": "DESCRIPTION",
      "direction": "REQUEST",
      "mandatory": "true",
      "type": "STRING",
      "description": "The descriptive text."
    },
    {
      "key": "3",
      "name": "API",
      "direction": "REQUEST",
      "mandatory": "true",
      "type": "RECORD_ARRAY",
      "description": "The API of the microservice.\nThe type of each record is CRecordDescriptionOfRecord."
    }
  ]
}

Message Arguments

Key Name Direction Mandatory Type Description
1 ID REQUEST true ID The ID of the microservice.
2 DESCRIPTION REQUEST true STRING The descriptive text.
3 API REQUEST true RECORD_ARRAY The API of the microservice.
The type of each record is CRecordDescriptionOfRecord.

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