Database Provisioning Framework Using Blueprint Templates

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current database platform implementations require manual and time-consuming processes for provisioning database objects when a customer switches to a new application, leading to errors and inconsistencies.

Innovation Solution

An automated application-provisioning framework that receives a provisioning request, retrieves an application-provisioning blueprint document, and provisions database objects such as users, roles, databases, and schemas, including creating a namespace, to facilitate seamless application access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual provisioning processes are used for database objects, then flexibility in handling unique cases is maintained, but time consumption and error rates increase

Engineering Contradiction:

Improveprovisioning process simplicityVSAvoidprovisioning time

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

The system performs preliminary actions by creating template database objects and blueprints in advance that define the structure and configuration of database objects. When provisioning is needed, the system retrieves and applies these pre-defined templates, eliminating the need for manual creation steps and significantly reducing provisioning time while maintaining consistency.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system uses copying by retrieving template database objects from storage and creating instances by applying these templates to specific customers or applications. This allows automated replication of standardized database structures, reducing manual effort and ensuring consistency across multiple provisioning events.

Inventive Principle:

Principle #26Copying

2Adaptability or versatility

If manual provisioning processes are used for database objects, then adaptability to specific requirements is maintained, but consistency and error rates deteriorate

Engineering Contradiction:

Improveprovisioning flexibilityVSAvoidprovisioning consistency

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system uses parameter changes by allowing templates to be configured with variable parameters that can be adjusted for different customers, applications, or requirements. This enables the same template framework to adapt to specific needs through parameter modification rather than manual restructuring, maintaining both consistency and adaptability.

Inventive Principle:

Principle #35Parameter changes

3Productivity

If automated provisioning framework is implemented, then provisioning time and consistency are improved, but system complexity increases

Engineering Contradiction:

Improveprovisioning efficiencyVSAvoidprovisioning system complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The system applies segmentation by dividing the provisioning process into distinct components: templates for database object definitions, blueprints for application-specific configurations, and a provisioning framework that coordinates them. This modular structure manages complexity by organizing functions into separate, reusable units that can be independently maintained and updated.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system uses an intermediary approach by introducing template objects and blueprint documents as intermediate layers between the provisioning framework and actual database objects. These intermediaries encapsulate complexity, allowing the framework to work with standardized interfaces while the templates handle the detailed configuration logic.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Reliability

If templates and blueprints are used for provisioning, then standardization is achieved, but adaptability to new applications may be reduced

Engineering Contradiction:

Improveprovisioning standardizationVSAvoidextension ease

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system applies universality by designing templates and blueprints with generic structures and parameters that can serve multiple applications and database object types. The framework is built to handle different application scenarios through configurable parameters rather than application-specific hardcoding, enabling both standardization and adaptability through a single unified system.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS11501010B2Application-provisioning framework for database platforms

Publication Date: 2022.11.15 SNOWFLAKE INC

AI summary

In an embodiment, an application-provisioning framework of a database platform receives a provisioning request from a requesting entity, requesting provisioning of an application for a customer account of the database platform. In response to receiving the provisioning request, the application-provisioning framework retrieves, from data storage, an application-provisioning blueprint document that lists one or more database objects. The application-provisioning framework provisions, according to the retrieved application-provisioning blueprint document, the one or more listed database objects in a database associated in the database platform with the customer account.