Denodo Architectures: Operational Workloads
You can translate the document:This document shows an architecture pattern for Operational workloads.
Operational Workloads
Unified Views of Business Entities
The semantic layer in this case is used to provide unified views of key business entities for enterprise operational applications that can get access to data in real time including transactional read-write support.
This is very useful for operational applications such as for instance a customer service desktop application that might require access to multiple business applications to properly attend a customer request.
Read/Write support for Operational Systems / Support for Autonomous Agents
The semantic layer in this case connects directly to enterprise operational systems and the user is able to carry out updates and inserts against the semantic layer, something that is required in an operational context. Autonomous agents can benefit from this support as they can automatically carry out operations against operational systems through this layer.
Operational Workloads
The workload in these types of scenarios usually consists of high concurrency queries that usually have to deal with small to medium data volumes. Queries are typically executed in the mili-second range and concurrency levels can be very high.
Protect operational systems for overloading
The Denodo Platform layer applies similar strategies to avoid or minimize the impact on operational systems such as enabling the cache or defining workload management policies using the Denodo Resource Manager.
When to use this Architecture Pattern
Apply this pattern when dealing with a number of heterogeneous operational applications and needing a single and unified view of key business entities for operational purposes. The semantic layer exposes unified views that can be easily consumed by any enterprise application. This layer can support high concurrency levels.
References
Logical Data Management Reference Architecture
Denodo Architectures: Logical Data Warehouse for Analytics
Denodo Architectures: Data Lake and Lakehouse
The information provided in the Denodo Knowledge Base is intended to assist our users in advanced uses of Denodo. Please note that the results from the application of processes and configurations detailed in these documents may vary depending on your specific environment. Use them at your own discretion.
For an official guide of supported features, please refer to the User Manuals. For questions on critical systems or complex environments we recommend you to contact your Denodo Customer Success Manager.
