TABLE OF CONTENTS
This chapter contains notational conventions, terms and acronyms definitions which are used in this document
1. Terms and Definitions
The following terms are used throughout this doucment.
Term | Definition |
Gateway | An application that handles all Web traffic to the microservices. |
Elastic | A search engine based on Lucene. It provides a distributed, multitenant-capable full-text search engine with an HTTP web interface and schema-free JSON documents. |
Multitenancy | An architectural feature of XME.digital allowing to provide a dedicated space (tenant) for each customer. |
Microservice | XME.digital applications, that handle REST requests. They are stateless, and several instances of them can be launched in parallel to handle heavy loads. |
Swagger | Is an open source software framework backed by a large ecosystem of tools that helps developers design, build, document, and consume RESTful Web services. |
2. Acronyms and Abbreviations
The following acronyms are used throughout this document.
Acronym | Definition |
API | Application Programming Interface |
APU | Action Processing Unit |
SOAP | Simple Object Access Protocol |
UI | User Interface |
URL | Uniform Resource Locator |
3. Notations
The following notational conventions are used in this document:
| Text preceded by this symbol is a part of a list. |
«» | Text enclosed by quotation marks is a reference to an artifact. |
1) | Text preceded by a number describes activities that should be performed in the fixed order. |
Prompt | Text represented by this colour is appeared as a part of document structure and intended to facilitate comprehension. |
Entity | Word that has began with a capital letter is a reference to an Entity. |
App | Text represented by this style indicates a Component or System. |
| (TBD) | Indicates incomplete information necessary to complete a requirement.
|
|
|
