Sparkle - LOGOSparkle - LOGO
  • Home
  • Agile Information Factory
  • Reference Architecture
  • Jobs
  • Blog
  • Contact

Reference Architecture

Based on the Agile Information Factory, we have developed a Reference Architecture which serves as a foundation to effectively and efficiently turn data into gold. We have a layered architecture which is geared for flexibility, scalability, cost efficiency and performance. By having a clear purpose for each layer and by defining clear rules on which transformations happen where, we have a predictable architecture which is ready to take your organization to the next level of data maturity.

Access Layer

This layer consists of the tools that are used for analyzing and reporting on information (think MS Power BI, SSRS). Typical usage includes strategic scorecards, operational dashboards, pixel-perfect reporting, ad-hoc queries, multidimensional analyses and the different flavors of analytics.

Presentation Layer

In the presentation layer the data is (virtually) transformed to a data model which is based on the information needs of the organisation and is geared towards reporting. These are typically star schemas. The presentation layer can always be rebuilt from scratch based on the data from the foundation layer.

Foundation Layer

The foundation layer is where we integrate the different data sources. The foundation layer is often modeled according to the Data Vault 2.0 methodology. In the foundation layer we will store a full history of the data on an atomic level.

Operational Layer

The operational layer contains detailed information on operational transactions and is typically loaded in a (near) real-time fashion. The goal is to support operational information needs. The data retention in the operational layer is typically limited in time. Historical changes are not maintained.

Data Lake

The data lake can contain structured, semi-structured and non-structured data. There is typically no schema on write, but a schema on read. Often used in support of data science.

Data Sources

This layer consists of the all the operational data sources in an organization. While this layer used to be typically OLTP systems, there’s quite some innovation in this area (cloud databases, social media, internet of things, service bus, …).

Data Lab

The data lab supports complex ad-hoc queries against a heterogeneous set of data sources. It functions as a sandbox to support data discovery, ad-hoc reporting and analytics. The data is only stored for a limited time. Once a specific analysis is required on a regular basis, it’s typically industrialized in the data warehouse.

Metadata

Metadata mainly consists of data lineage and impact analysis. Data Lineage: trace where data in the reporting and analytics is coming from and which operations were performed on it. Impact Analysis: Analyse the impact on the Data Warehouse environment when changing source systems. Finally, a well governed business glossary will help to align on business term definitions.

Integration Components

The different integration components which embed and integrate the data architecture within the existing IT landscape. This typically includes a portal (like (Azure) Sharepoint) to share information and reports within the organization, an authentication and authorization provider (like (Azure) Active Directory) or a Graphical Information System which allows to visualize information on a geographical map.

© Sparkle 2019, All rights reserved. Privacy Policy. Built by Sidekick.
Manage cookie consent
To provide the best experiences, we use technologies like cookies to store and/or access device information.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage options Manage services Manage vendors Read more about these purposes
View precerences
{title} {title} {title}