Serverless Data Representation Service for Multi-Modal ML Featurization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current machine learning platforms lack automated tools for data ingestion and featurization across multiple data modalities, requiring significant manual effort from data scientists and resulting in suboptimal performance.
Innovation Solution
A cloud-based Data Representation-as-a-Service (DRaaS) system that generates and provides vector representations of input data objects, allowing data scientists to focus on downstream ML model training without manual feature engineering, and enabling flexible customization for various use cases.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If data scientists use manual coding and experimentation with different data representation techniques for each modality, then they can try early or late fusion ML models, but the process becomes very time consuming and often leads to models that are not the best performing
Solution Approach 1:
The system pre-generates data representations (features) for multiple data modalities before the ML modeling process. This preliminary action eliminates the need for data scientists to manually code feature engineering for each modality during model development, significantly reducing the time-consuming experimentation process while maintaining or improving model performance through optimized pre-computed representations.
Solution Approach 2:
The system automatically performs data representation generation and feature engineering without requiring manual coding by data scientists. The automated service handles the complex process of creating optimized data representations for different modalities, allowing data scientists to focus on model selection and training rather than manual feature engineering, thus reducing time investment while achieving better model performance.
2Extent of automation
If there is no automated data ingestion and featurization service, then data scientists can maintain control over the process, but they lack tools and frameworks that can provide automated data ingestion and featurization for multiple modalities
Solution Approach 1:
The system provides a universal data representation service that handles multiple data modalities (text, images, audio, video, tabular data) through a single unified interface. This multi-functional approach automates data ingestion and featurization across different modalities without requiring separate complex systems for each data type, thereby increasing automation extent while managing system complexity through consolidation.
Solution Approach 2:
The system acts as an intermediary service between raw multi-modal data and ML models. It provides automated data ingestion and featurization by receiving various data modalities, processing them through appropriate representation techniques, and outputting standardized features that can be directly used by ML models. This intermediary layer simplifies the overall system architecture by centralizing the complex data processing logic.
3Adaptability or versatility
If existing AI services are used, then they can provide pre-defined functions, but they are rigid and focused on pre-defined use cases without allowing flexibility or customization
Solution Approach 1:
The system provides dynamic and flexible data representation generation that can be customized for different use cases and modalities. Unlike rigid pre-defined AI services, this system allows data scientists to select and configure appropriate representation techniques based on specific requirements, enabling adaptation to various scenarios while maintaining ease of operation through a unified service interface that handles the complexity internally.
Data Source
AI summary
Techniques for enabling the building of general input data ML flows using a serverless data-representation-as-a-service (DRaaS) are provided. In one technique, in response to receiving a first data representation (DR) generation request from a first calling entity, first input data is retrieved based on the first DR generation request, a first set of DRs is generated (by a DR generator) based on the first input data, and the first set of DRs are made available to the first calling entity. In response to receiving a second DR generation request from a second calling entity that is different than the first calling entity, second input data is retrieved based on the second DR generation request, a second set of DRs is generated based on the second input data, and the second set of DRs are made available to the second calling entity.


