OrcaHouse is the project. The project comprises Enterprise Data Warehouses (EDW). The term “OrcaHouse” kept as high level project concept.
OrcaHouse mainly follows implementation of “Enterprise Data Warehouse” architecture. Alternate would be “Data LakeHouse” architecture. There are subtle differences in how you approach to data modelling based on the architecture choice being made.
OrcaVault is the first EDW of OrcaHouse. Its main objective is to build the data warehouse need of our upstream OrcaBus system.
As mentioned, our upstream OrcaBus system is based on “Event-driven” “Microservice” architecture. The system comprises many smaller-sized transactional databases. These microservices may come and go (being replaced) as it pivots to new business requirement. OrcaVault EDW aims to capture, consolidate, observe, archive and history track these changes. Provide business intelligence and audit trail.
Please read high level architecture note to understand the overall data flow and data layers within the warehouse.
Federated query is possible via OrcaHouse Athena setup.