...
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 standardenterprise grade layers, any business solution must address to seamless integrate, run and scale inside an enterprise, so PIPEFORCE does. Below you can find a mapping from these 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.
In PIPEFORCE:
Data Pipelines
Functions
Scripts
Microservices
Data Access Layer
Responsible for data management and interaction with databases.
In PIPEFORCE:
Property Store
Integration Layer
Facilitates communication between different systems and services, often through APIs or middleware.
In PIPEFORCE:
Commands & Connectors
API Gateway
Webhooks
Workflow Layer
Coordinates processes and workflows within the system.
In PIPEFORCE:
Workflow Service (Camunda)
Workflow Designer
Taskview
Security and Management Layer
Focuses on authentication, authorization, logging, and security management.
In PIPEFORCE:
Log Service
Log View
OAuth via KeyCloak
Microservice Layer
Manages and provides services used by the application or other systems.
In PIPEFORCE:
services.* commands in order to start / stop microservices
Services UI
Application Infrastructure Layer
Provides the infrastructure necessary for the application, including servers and cloud services.
In PIPEFORCE:
Kubernetes
Caching Layer
Responsible for storing frequently accessed data to reduce latency.
In PIPEFORCE:
Redis
In Memory-Caching in hub
Hibernate Cache
Orchestration Layer
Coordinates complex workflows and service interactions, often in microservice architectures.
In PIPEFORCE:
Kubernetes
Services UI
service.* commands
Reporting and Analytics Layer
Handles business intelligence, analytics, and reporting functions.
In PIPEFORCE:
Reporting Framework
Identity and Access Management (IAM) Layer
Manages user identities and controls access to system resources.
In PIPEFORCE:
IAM (KeyCloak)
Audit Layer
Captures logs and audit data for compliance.
In PIPEFORCE:
Audit Logging
Communication & Messaging Layer
Manages communication between services, often using messaging systems.
In PIPEFORCE:
RabbitMQ
Security Architecture Layer
Provides security mechanisms across all system layers, including encryption and SSL/TLS.
In PIPEFORCE:
HTTPS with external
Encrypted storage
Encrypted secret management
Notification Layer
Manages notifications and real-time alerts for users or systems.
In PIPEFORCE:
(Push) Notification Framework
Monitoring and Logging Layer
Focuses on system health monitoring, performance metrics, and logging.
In PIPEFORCE:
Via Google Cloud Monitoring
Log Viewer
Commands
External Tools / connects