Pangeanic Corporate Solution Architecture: Difference between revisions
Jump to navigation
Jump to search
Line 13: | Line 13: | ||
=== SaaS - Service Area=== | === SaaS - Service Area=== | ||
That area includes the technical resources to be able to serve users' requests and includes: | That area includes the technical resources to be able to serve users' requests and includes as main blocks: | ||
*'''Interfaces''': a web interface and a restful API | *'''Interfaces''': a web interface and a restful API used by users, robots or programatically to access the solution functionality | ||
*The ''' | *The '''HUB''' receiving and rerouting the users requests. The physical implementation varies from a single micro server to a kubernetes managed platform with load-balancing and upscalation in order to server up-to thousands of requests per second. | ||
*The File Procesor, in charge of extract text data from formated documents and to re-build them with minimal format loss. | |||
*Users access the functionalities with a variety of client interfaces (described later) such as the PGB, Web applications, CAT tools or programmatically with a RESTFul API for integrations. | *Users access the functionalities with a variety of client interfaces (described later) such as the PGB, Web applications, CAT tools or programmatically with a RESTFul API for integrations. |
Revision as of 15:50, 3 December 2021
Pangeanic Architecture Block Diagrams
The diagram shows the different logical blocks.
The solution is implemented on a fully distributed architecture with different modules and covers 3 main areas:
- SaaS - Service Area
- Data Management
- Machine Learning
SaaS - Service Area
That area includes the technical resources to be able to serve users' requests and includes as main blocks:
- Interfaces: a web interface and a restful API used by users, robots or programatically to access the solution functionality
- The HUB receiving and rerouting the users requests. The physical implementation varies from a single micro server to a kubernetes managed platform with load-balancing and upscalation in order to server up-to thousands of requests per second.
- The File Procesor, in charge of extract text data from formated documents and to re-build them with minimal format loss.
- Users access the functionalities with a variety of client interfaces (described later) such as the PGB, Web applications, CAT tools or programmatically with a RESTFul API for integrations.
- The Production Access Server manages user requests and orchestrates the rest of modules. It requires a standard SQL database to store the required data to fulfil the requests.
- The engines, either local (managed by the organization on their own premises or on their own cloud) or operated by Pangeanic with a SaaS model will perform the actual language processing.
- A file processor is in charge of dealing with converting files and documents when this feature is installed.
- An on-line trainer module is in charge of evolving the models according to the user preferences. This is integrated in the engine package when the on-line learning option is installed.