Business Data Lake Conceptual Framework
Download 493.56 Kb.
|
- Navigate this page:
- Actions – Service Layer
Business compartmentsThe goal of the BDL is to serve multiple lines of business. Analytics are often designed and executed within a specific business context. They generate data that also may be specific to this context. Moreover, performance requirements also depend on the criticality of specific business contexts. For the previous reasons, the BDL should enforce the capability to deal with multiple “vertical” specific business compartments. It should be possible for most BDL concepts (at least data, ingestion, analytics, analytics engines and governance rules) to be defined both globally or within one or several bBusiness compartments. Sandbox environments can be considered as business compartments attached to “light” governance contexts, for early-stage discovery analytics. For business critical missions powered by mature analytics, high-performance environementenvironment should be created with a strict access policy. Actions – Service Layer
Actions are the main concept of the Service Layer, which actually deliver Insights to the point of actions outside of the Business Data Lake. Actions can be delivered either to human end-users or to “automated” applications endpoints. Common identified action types are: Querying data to assemble valuable pieces into consistent information. Search capabilities enter this category. Visualizing Data Queries into a Self-Service BI Environment. These Environments enables end-users to design their own “reports” that leverage simple visualization techniques (filters, charts, drill down, etc) and potentially any Data from the Business Data Lake they are allowed to access. Leveraging Big Data Apps, which are applications specifically built on top of the Business Data Lake. Big Data Apps can use common services hosted by the Business Data Lake, for instance for querying data or scheduling jobs. Delivering Insights to existing applications and endpoints in the Enterprise landscape. Message brokers and ESBs can implement this kind of actions. Directory: bigdata bigdata -> Use Cases from nbd(nist big Data) Requirements wg bigdata -> Use Cases from nbd(nist big Data) Requirements wg 0 bigdata -> Nist big Data Public Working Group (nbd-pwg) nbd-pwd-2015/6a,DW. abbreviated rr (M0444) Source: nbd-pwg status: Draft Title: Big Data Use Case #6 Implementation, using nbdra author: Afzal Godil bigdata -> Nist special Publication 1500-4 draft: nist big Data Interoperability Framework: Volume 4, Security and Privacy Download 493.56 Kb. Share with your friends:
|