Data Lake Management
AWS Lake Formation
Data lake setup, governance, and access controls.
AWS
Service information
AWS Lake FormationShortname: Lake Formation
Huawei equivalent shortnames: Lake Formation, DataArts Fabric
Keywords: data lake, governance, catalog
Differences vs Huawei
- Permission and catalog constructs differ.
Migration to Huawei
- Map ingestion, transformation, query semantics, and governance/metadata dependencies. For AWS AWS Lake Formation, the direct Huawei equivalence layer is Lake Formation + DataArts Fabric; validate feature-by-feature parity for control plane, data plane, and operational behavior before cutover.
- Use a composed Huawei migration pattern where needed: DataArts Fabric + DGC + OBS. Treat Lake Formation + DataArts Fabric as the core equivalent capability and use the additional services to cover integration, security, observability, and governance gaps.
- Pricing model difference: AWS usually bills query/compute runtime, scanned or processed data, and storage; Huawei usually bills DLI/DWS/MRS/CDM runtime or cluster-spec billing plus storage and transfer. Recalculate TCO with peak load, request volume, retention period, and cross-region/interconnect traffic before production migration.
Huawei Cloud
Huawei equivalent service
DataArts FabricShortname: DataArts Fabric
General function: Data Governance
Unified data fabric and governance capabilities.
Keywords: data fabric, governance, catalog
Huawei equivalent service
DataArts Lake FormationShortname: Lake Formation
General function: Data Lake Management
Data lake formation and governance capabilities.
Keywords: data lake, governance, metadata