Microservices

Table of Contents

• Subservices
• Accessing Microservices

Microservices provide packaged functionality. A microservice can provide tasks, events, and/or attributes. The exact functionality and feature set differs from microservice to microservice. A microservice may, for example, provide a PID controller, drive a display, or push data to the cloud.

Microservices are provided by service providers. Xentara has a built-in service provider for debugging. Other service providers may be installed via plugins.

Subservices

Some types of microservices can have subservices. A subservice is simply a microservice that is a child of another microservice. The Xentara MQTT client service provider, for example, exposes one microservice for wach MQTT broker it connects to, and one child microservice for each MQTT topic it publishes to that broker:

Accessing Microservices

Microservices have at least the following members:

Attributes

key	The microservice’s primary key.
name	The microservice’s name. The name is the last component of the primary key.
UUID	The unique UUID of the microservice.

Each individual type of microservice can have additional members. Most microservices will have a task to execute them, for example. Please refer to the documentation of the specific microservice for details.

To refer to a member, use its primary key. The primary key of the UUID attribute of a microservice called “My.Micro.Service” is “My.Micro.Service.UUID”.