Describing IT Services and Micro-services
An IT service is a component of an application made available to the end user of the application in the context of his/her work.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.Prerequisite
You must first define a work environment for a project in progress. See "Le volet Projet en cours", page 22.
Defining an IT Service or a Micro-Service
Accessing the list of IT services
To access the list of IT services using the Current Design Project navigation pane:
Select Application Architecture Design > IT Services .The list of IT services appears in the edit area.
Accessing the list of micro-services
To access the list of micro-services using the Current Design Project navigation pane:
Select Application Architecture Design > Micro-Services .The list of micro-services appears in the edit area.
Properties of an IT Service or a Micro-Service
The complete description of an IT service or 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.
For more details on software technologies, see HOPEX IT Architecture.Using an IT or Micro-Service Flow Scenario
For more details on scenarios of flows diagrams, see Describing a scenario of flows.A micro-service flow scenario represents the flows exchanged between certain elements of the micro-service in a given context. The elements represented are:
• IT services,
• micro services,
• stores of local or external application data,
• input or output application ports.
The interactions offered between these elements:
• application flows that carry a content,
• application flow channels that group a number of application flows on a single link,
• application data channels that represent the interactions between the application data stores.
Using the IT Service or Micro-Service Structure Diagram
For more details on structure diagrams, see Creating a structure diagram.With HOPEX Application Design, the components of a micro-service can be described by a micro-service structure diagram.
This type of diagram includes:
• IT services,
• micro services,
• RE or RDB external data stores; see "Utiliser les dépôts de données", page 72.
• access, request and service points; Describing Service and Request Points.
• interactions between 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.