Other methodologies are available for use; however, the DV2 methodology is uniquely
geared to leverage the benefits of the DV2 model, process designs, and much more.

A Technical View

The methodology (like the modeling components) is based on solid repeatable process
designs. These designs require little to no reengineering and can handle scale-out, scale-
up, parallelism, and real time with ease. The methodology is also geared around the
people. From a technical standpoint, there is nothing better than having an agile team,
capable of implementing and rapidly scaling a solution.

Tooling that is offered by both AnalytiX DS and WhereScape assists the team from the
process perspective. Automation and generation tooling is beneficial in increasing the
delivery speed by a factor of four times (minimum).

Why Do We Need a Data Vault 2.0 Architecture?

Data Vault 2.0 architecture is designed to include NoSQL (think: big data, unstructured
data, multistructured, and structured data sets). Seamless integration points in the model,
and well-defined standards for implementation offer guidance to the project teams.

DV2 architecture includes NoSQL, real-time feeds, and big data systems for unstructured
data handling and big data integration. The DV2 architecture also provides a basis for
defining what components fit where and how they should integrate. In addition, the
architecture provides a guideline for incorporating aspects such as managed self-service
BI, business write back, natural language processing (NLP) result set integration, and
direction for where to handle unstructured and multistructured data sets.

Where Does Data Vault 2.0 Implementation Fit?

DV2 implementation focuses on automation and generation patterns for time-savings,
error reduction, and rapid productivity of the data warehousing team. The DV2
implementation standards provide rules and working guidelines for high-speed reliable
build-out with little to no errors in the process. The DV2 implementation standards
dictate where and how specific business rules are to execute in the process chain,
indicating how to decouple the business changes or data provisioning from data
acquisition.

Chapter 6.1: Introduction to Data Vault 2.0