HOPEX IT Architecture V2 > Modeling Technical and Functional Architectures > Describing Application Architecture > Describing a Micro-Service with HOPEX IT Architecture
Describing a Micro-Service with HOPEX IT Architecture
*A micro-service is a software component that can be deployed autonomously, but which does not directly provide an end user service. It can interact with other application services, applications or application systems. This is a deployable software component that uses software technologies. For example: an authentication service, a PDF file printing service.
Accessing the list of micro-services  
To access the list of micro-services from the Application Architecture navigation pane:
*Select Functional Architecture > Micro-Services.
The list of micro-services appears in the edit area.
Micro-Service properties with HOPEX IT Architecture 
The complete description of a micro-service is accessed from its properties pages.
The Characteristics properties page for a micro-service provides access to:
• its Owner, by default, during creation of the micro service, the current library.
• its Name,
• the text of its Description.
• the Technologies section provides access to the list of software technologies used by the micro-services.
*A software technology is a basic component necessary for operation of business applications. Software technologies include all basic software such as: application server, electronic mail server, software components for presentation, data entry, storage, business information sharing, operating systems, middleware, navigators, etc.
*For more details on software technologies, see Describing a Software Technology.
With HOPEX IT Architecture a micro-service is described by other property pages. See HOPEX IT Architecture properties pages content.
Using the IT Service and Micro-Service Structure Diagram 
*For more details on use of a structure diagram, see Creating a structure diagram
With HOPEX IT Architecture, the components of an IT Service can be described by an IT Service structure diagram.
In the same way, the components of a micro-service can be described by a micro-service structure diagram.
These two diagrams include:
• IT services,
• micro services,
• Physical data stores; see Managing Data.
• access, request and service points; Describing Service and Request Points.
• interactions between the components
*An interaction represents a contract established in a specific context between autonomous entities that are internal or external to an enterprise. These entities can be enterprise org-units, applications, activities or processes, as well as external org-units. The content of this contract is described by an exchange contract.