# How to Automatically Deploy Database Containers Based on Workload Patterns > This patent describes a method for automatically deploying optimized database containers by analyzing storage system data to identify workload "fingerprints" and matching them to specific container configurations. - **Patent:** US 12737226 - **Original title:** Fingerprint-based database container deployment - **Granted:** 2026 - **Status:** Active - **Times cited:** 0 - **Field:** software, telecommunications, cloud_computing, data_management ## What it does The patent describes a system for smart deployment of database containers. It starts by gathering information from one or more storage systems in a storage environment to identify "characteristics of a plurality of database workloads." For example, it might analyze data access patterns or I/O demands. Based on these characteristics, the system then identifies "fingerprint information for a plurality of database workload types." This fingerprint acts like a unique profile for how a database is used. Finally, when a new database container is needed, the system uses this "fingerprint information for a particular database workload type" to deploy a database container specifically configured for that workload, aiming for better performance and resource use. ## What it does NOT cover - Does not cover deploying database containers without first identifying workload characteristics from storage system data. - Does not cover deploying containers based solely on manual configuration or generic templates without generating "fingerprint information." - Does not cover general container deployment for applications that are not databases. - Does not cover systems that identify workload types without specifically collecting data from "one or more storage systems." - Does not cover identifying database workload types without creating specific "fingerprint information" for them. ## The clever bit The novelty lies in creating specific "fingerprint information" from observed database workload characteristics on storage systems to automatically guide the deployment of optimized database containers. This moves beyond generic container deployment to intelligent, data-driven optimization. ## Real-world examples 1. Cloud database services like AWS RDS or Google Cloud SQL 2. Kubernetes deployments for stateful database applications 3. Database-as-a-Service (DBaaS) platforms 4. Data centers managing large numbers of virtualized databases ## Why it matters This technology aims to make database operations more efficient by automating the optimization of container deployments. In large cloud environments or data centers, manually tuning database containers for every workload is complex and time-consuming. By automatically matching container configurations to specific workload patterns, this patent could lead to better performance, reduced resource consumption, and lower operational costs for companies managing many databases. ## Frequently asked questions ### What does How to Automatically Deploy Database Containers Based on Workload Patterns cover? This patent describes a method for automatically deploying optimized database containers by analyzing storage system data to identify workload "fingerprints" and matching them to specific container configurations. ### When does this patent expire? This patent is expected to expire on September 15, 2046, when the invention enters the public domain. ### What problem does this patent solve? This technology aims to make database operations more efficient by automating the optimization of container deployments. In large cloud environments or data centers, manually tuning database containers for every workload is complex and time-consuming. By automatically matching container configurations to specific workload patterns, this patent could lead to better performance, reduced resource consumption, and lower operational costs for companies managing many databases. ### What does this patent NOT cover? Does not cover deploying database containers without first identifying workload characteristics from storage system data. **Full plain-English explainer:** https://patentbrief.org/patent/us/12737226/fingerprint-based-database-container-deployment **Original patent:** https://patents.google.com/patent/US12737226 --- _Source: PatentBrief — https://patentbrief.org. Patent facts are from public records; the plain-English explanation is PatentBrief's._ ## Related patents Semantically similar inventions in the PatentBrief corpus: - [How Computers Automatically Adjust Tasks to Run Faster in Data Centers](https://patentbrief.org/patent/us/9405582/aws-elastic-beanstalk) — A method for cloud computers to monitor their own performance while processing massive data tasks and automatically changing their settings or resource levels to stay efficient. - [How Virtual Machines Keep Their Data Separate on Shared Storage](https://patentbrief.org/patent/us/9760393/azure-machine-learning) — A method for virtual machines to store data in isolated, non-mixed logical storage units to improve security and management efficiency within a shared physical storage pool. - [How Software Automatically Translates Database Queries for Different Storage Systems](https://patentbrief.org/patent/us/9535948/facebook-watch) — A system that intercepts database queries written for traditional relational databases and automatically translates them to work with non-relational databases, allowing developers to switch storage systems without rewriting their application code. - [How a Single Command Deploys Cloud Infrastructure Automatically](https://patentbrief.org/patent/us/12739267/automated-cloud-infrastructure-deployment) — This patent describes an automated system that takes one command to deploy computing resources across different cloud platforms using various Infrastructure as Code tools, then connects them to a monitoring system. - [How Cloud Systems Automatically Assign Virtual Machines to Servers](https://patentbrief.org/patent/us/9075661/hyper-v-virtualization) — A method for cloud services to automatically choose the best server for a task by filtering out impossible options and then ranking the remaining ones.