<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <title>Data lakehouse architecture for self-service data analytics</title>
  </titleInfo>
  <name type="personal">
    <namePart>Soon, Kien Yuan</namePart>
    <role>
      <roleTerm authority="marcrelator" type="text">creator</roleTerm>
    </role>
    <role>
      <roleTerm type="text">author.</roleTerm>
    </role>
  </name>
  <typeOfResource>three dimensional object</typeOfResource>
  <originInfo>
    <place>
      <placeTerm type="code" authority="marccountry">my</placeTerm>
    </place>
    <dateIssued encoding="marc">2023</dateIssued>
    <copyrightDate encoding="marc">2023</copyrightDate>
    <issuance>monographic</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
  </language>
  <physicalDescription>
    <form authority="marcform">electronic</form>
    <extent>xii, 80 pages : illustrations ; 1 CD-ROM.</extent>
  </physicalDescription>
  <abstract>This project focuses on designing and implementing a Data Lakehouse architecture to  facilitate self-service analytics. The objectives include creating a collaborative analytics  environment, streamlining the management of multiple ETL processes, adopting a costeffective and non-proprietary architecture, integrating with BI tools, ensuring high query  performance for interactive visualization, enabling data warehousing capabilities, and  offering a self-service data discovery and metadata platform. The project followed an  iterative development methodology that involves requirement gathering and planning,  design, implementation, testing, deployment, and maintenance phases. The logical design  consists of six layers which are data ingestion, storage, catalog, semantic, processing, and  consumption. The physical design utilized Dremio as the core component, along with  Apache Iceberg and Arrow Flight Engine for data format and query processing. The  project also adopted an Integrated Multi-Zone Analytics Framework to handle different  data tasks and workloads. The implementation was performed using Docker, and the  testing validates the achievement of the objectives. Deployment was done on an Azure  Kubernetes Service (AKS) cluster, although the deployment of the Dremio cluster is  hindered due to budget and resource limitations. Maintenance activities included security,  backup, node monitoring, cost usage, configuration tuning, metadata management, and  training and support. This project concludes that the objectives have been achieved and  suggests some future enhancements, such as using Project Nessie for catalog storage,  considering Dremio Enterprise Edition for advanced features, and exploring Databricks  and MLflow if expecting extensive machine learning workloads.</abstract>
  <targetAudience authority="marctarget">specialized</targetAudience>
  <note type="statement of responsibility">Soon Kien Yuan</note>
  <note>Center for Mathematical Sciences</note>
  <note>Bachelor of Applied Science In Data Analytics With Honour -- Universiti Malaysia Pahang – 2023</note>
  <note>Includes bibliographical references</note>
  <subject authority="lcsh">
    <name type="corporate">
      <namePart>Center for Mathematical Sciences</namePart>
    </name>
    <topic>Dissertations</topic>
  </subject>
  <subject authority="lcsh">
    <topic>Universities and colleges</topic>
    <topic>Dissertations</topic>
  </subject>
  <subject authority="lcsh">
    <topic>Final Year Report</topic>
    <topic>Dissertations</topic>
  </subject>
  <identifier type="isbn">THE0010027 (Local)</identifier>
  <recordInfo>
    <recordContentSource authority="marcorg">UMPSA</recordContentSource>
    <recordCreationDate encoding="marc">250505</recordCreationDate>
    <recordChangeDate encoding="iso8601">20251125111037.0</recordChangeDate>
    <languageOfCataloging>
      <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
    </languageOfCataloging>
  </recordInfo>
</mods>
