...
In this last tier, the system is operated in production. Once a solution has been tested successfully on the QA tier it can be moved to the PROD tier.
The standard layers of PIPEFORCE
There are standard enterprise grade layers, any business solution must address to seamless integrate, run and scale inside an enterprise, so PIPEFORCE does.
Usually, for any of these layers at least one technical expert and sometimes also a bigger team of software engineers and technical experts is required to implement and/or maintain the specific layer. But since PIPEFORCE is a turnkey solution, most of these layers are already covered by the maintenance subscription fee without extra cost or can be easily implemented and maintained by non-technical users using our Low Code, No Code and AI toolings.
Below you can find a mapping from the enterprise standard layers to the sections in the documentation for faster navigation.
Presentation Layer
This layer handles the user interactions and interfaces like forms and lists.
Business Logic & Data Processing Layer
Manages business logic and rules for data processing. Deals with processing operations on data, including computation and applying logic. Handles document evaluation, extraction, and processing, applying business logic and rules.
Data Access Layer
Responsible for data management and interaction with internal and external databases.
Integration Layer
Facilitates communication between different systems and services, often through APIs or middleware.
Workflow Layer
Coordinates stateful processes and workflows where manual steps and interactions with humans are required within the system.
Security and Management Layer
Focuses on authentication, authorization, encryption, logging, and security management.
Microservice Layer
Provides a runtime environment to execute, scales and manage microservices and containers.
Application Infrastructure Layer
Provides the infrastructure necessary for the application, including servers and cloud services.
PIPEFORCE runs entirely Cloud Native inside Kubernetes.
Can by hosted on any hyperscaler (like Google Gloud, AWS or Azure for example) or OnPremises in a private cloud.
Caching Layer
Responsible for storing frequently accessed data to reduce latency.
Different types of caches in the backend.
Orchestration Layer
Coordinates complex workflows and service interactions, often in microservice architectures.
Built-in in infrastructure and backend architecture.
Reporting and Analytics Layer
Handles business intelligence, analytics, and reporting functions.
Identity and Access Management (IAM) Layer
Manages user identities and controls access to system resources.
Audit Layer
Captures logs and audit data for compliance.
https://logabit.atlassian.net/wiki/spaces/PA/pages/2548465885/Logging%2C+Tracing+and+Monitoring
Communication & Messaging Layer
Manages communication between services, often using messaging systems.
Security Architecture Layer
Provides security mechanisms across all system layers, including encryption and SSL/TLS.
Allows only HTTPS communication with external
Encrypted storage
Encrypted secret management
https://logabit.atlassian.net/wiki/spaces/PA/pages/2548465885/Logging%2C+Tracing+and+Monitoring
Notification Layer
Manages notifications and real-time alerts for users or systems.
Monitoring and Logging Layer
Focuses on system health monitoring, performance metrics, and logging.
Integrate external Monitoring and Logging tools via REST API.
AI Layer
The artificial intelligence (AI) layer helps to speed up implementation and operation time and helps in optimizations afterwards.
Document Understanding Components
ChatBot integrations
Data Mapping Support
Security Checks
Automated workflow creation and optimization