> For the complete documentation index, see [llms.txt](https://docs.bdb.ai/pre-sales/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bdb.ai/pre-sales/manufacturing-use-case/non-functional-requirements/availability.md).

# Availability

* [x] &#x20;**Requirement:** Data platform must be installed and configured in high availability to be able to manage any "failures" and the maintenance activities for each critical component. The preferred configuration should be such that it can flexibly manage the failure of individual components and the redistribution of services to optimize the use of hardware resources. Failover mechanism should be automatic to ensure continuity of services. Please describe how the proposed topology ensures high availability (including data, metadata etc.).&#x20;
* [x] **BDB Response**: Yes. There are two typical environments where high availability would be implemented:&#x20;

Single Server with Hot Back-up: In this scenario, BDB Platform would be installed on a single server, and would also be installed on a hot back-up server. The hot back-up server would remain offline but would also be kept in-synch with the production server’s database through clustering until the time that the primary server failed. At that time the back-up server would kick in and all traffic would be re-directed.&#x20;

Multiple Server failover: In this scenario, BDB Platform would be installed across multiple servers. If at any point in time a server were to fail the other servers would automatically activate and take up the work of the failed server.

* [x] **Requirement:** Solution robustness, flexibility, and scalability.
* [x] **BDB Response**: Extend the value of your data across your entire organization with BDB Platform. Empower your business with the freedom to explore data in a trusted environment—without limiting them to predefined questions, wizards, or chart types. Have the peace of mind that both your data and your analytics are governed, secure, and accurate. Enterprises love BDB Platform for its ease of deployment, robust integration, simplicity of scalability, and excellent reliability. You no longer have to choose between empowering the business or protecting your data—with BDB Platform you can finally do both.&#x20;

Deeply integrate with your enterprise architecture to leverage technology investments. Choose from on-premises or public cloud and configure servers, manage software upgrades, or scale hardware capacity according to your requirements. Connect to any data and turbocharge teamwork by discovering, sharing, collaborating, and exploring data from mobile device, tablet, or computer. Build and scale mission-critical analytics while maintaining control with BDB Platform offering increased scalability, improved efficiency, and enhanced security. Monitor usage in one environment to more efficiently stay in compliance.&#x20;

Centralized governance, visibility, and control ensures your data is in the right hands with easy, automated authentication and permissions management. Integrate with your single sign-on (SSO) or identity provider. Curate, publish, and share data sources as live connections or encrypted extracts for everyone to use. Built into the platform, BDB Data Pipeline scales trusted data in a simple, repeatable way with BDB Data Catalog, BDB Data Preparation & BDB DS Lab, and Virtual Connections.&#x20;

* [x] **Requirement:** Approach for the transition to end state solution architecture for the data platform with tool overlay –
* [x] **BDB platform**: Following is the high-level plan -

#### First 3 Months –

* Core Architecture, Deployment etc. in the initial 3-4 weeks.
* Creation of Data Pipelines + Basic Data Enrichment + Data Clean-up= Data Lake.
* Quick Self Service Reports to show the output these DBs and something that use can see and give feedback.
* Start basic Advance Analytics Model Developments here.                &#x20;

#### Next 3 Months (4-6 Months) 

* Next 45 Days – Another version of Data Lake with Live use can see and give feedback
* &#x20;Next 45 days – Another Drop with Data Lake on Live Feeds + social media + APIs+ Other DB’s    with Self Service Reports
* Take the Model Developments to next level – all Regressions, Clusters, etc. for the Segmentation and Recommendation Models
* Dashboard development starts in this phase for the Data Lake created in first 3 months

{% hint style="info" %} <mark style="color:green;">Please Note</mark>: *The Models need to be trained and should be able to consume all necessary datasets for 6 months before we can put them on Parallel Ru&#x6E;**.***
{% endhint %}

#### Finalization of Data Lake – next 3 months \[7-9 months]

* Iteration 2 of Datal lake – Data Lake Finalization – Based on Self Service Reports and basic dashboards.

#### Visuals to be started formally after 6 months – till 12 months 

* All Dashboard Development and Signoff &#x20;
* All Models to be trained

#### 3 Months Parallel Run

* Production Deployment in Parallel&#x20;
* Further Model Training and its performance &#x20;
* Visualizations running with User acceptance or Feedback taken
* Performance Tunning of Infra + all other levels&#x20;
* Basic Support team is in Place

#### The performance Stage

* 16-18th Month (3 Months) &#x20;
  * Optimization of Algo’s and Further Training 
  * Changes in Visuals with next iteration
* Same as a for 3 months 
* Same as b for 3 months &#x20;
* 24 Months the Solution is optimized and working as one of the Best in the industry and surpassing the accuracy or performance.

- [x] **Requirement:** Infrastructure sizing and technical deployment for each proposed data platform component for Dev, UAT and Production environments.&#x20;
- [x] **BDB platform**: The below given table gives infrastructure sizing for Development environment –&#x20;

<table><thead><tr><th width="154">Region</th><th width="156">Description</th><th width="143">Service</th><th>Configuration Summary</th></tr></thead><tbody><tr><td>US East (Ohio)</td><td>BDB k8s cluster</td><td>Amazon EKS</td><td>Number of EKS Clusters (1)</td></tr><tr><td>US East (Ohio)</td><td>worker nodes</td><td>Amazon EC2</td><td>Operating system (Linux), Quantity (4), Pricing strategy (On-Demand Instances), Storage amount (150 GB), Instance type (m6g.4xlarge)</td></tr><tr><td>US East (Ohio)</td><td>Kafka</td><td>Amazon Managed Streaming for Apache Kafka (MSK)</td><td>Storage per Broker (1000 GB), DT Inbound: Not selected (0 TB per month), DT Outbound: Not selected (0 TB per month), DT Intra-Region: (0 TB per month), Data transfer cost (0), Do you want to setup any Kafka Connect connectors? (No), Number of Kafka broker nodes (3), Compute Family (m5. xlarge)</td></tr><tr><td>US East (Ohio)</td><td></td><td>Amazon RDS for MySQL</td><td>Storage for each RDS instance (General Purpose SSD (gp2)), Storage amount (50 GB), Quantity (1), Instance type (db.t4g.xlarge), Utilization (On-Demand only) (100 %Utilized/Month), Deployment option (Multi-AZ), Pricing strategy (OnDemand)</td></tr><tr><td>US East (Ohio)</td><td>storage</td><td>Amazon Elastic Block Store (EBS)</td><td>Number of volumes (1), Average duration each instance runs (730 hours per month), Storage amount per volume (3000 GB), Snapshot Frequency (Daily), Amount changed per snapshot (3 GB)</td></tr></tbody></table>

The below-given table gives infrastructure sizing for UAT environment –

<table><thead><tr><th width="127">Region</th><th width="164">Description</th><th width="185">Service</th><th>Configuration Summary</th></tr></thead><tbody><tr><td>US East (Ohio)</td><td>BDB k8s cluster</td><td>Amazon EKS</td><td>Number of EKS Clusters (1)</td></tr><tr><td>US East (Ohio)</td><td>worker nodes</td><td>Amazon EC2</td><td>Operating system (Linux), Quantity (4), Pricing strategy (On-Demand Instances), Storage amount (150 GB), Instance type (m6g.4xlarge</td></tr><tr><td>US East (Ohio)</td><td>Kafka</td><td>Amazon Managed Streaming for Apache Kafka (MSK)</td><td>Storage per Broker (1000 GB), DT Inbound: Not selected (0 TB per month), DT Outbound: Not selected (0 TB per month), DT Intra-Region: (0 TB per month), Data transfer cost (0), Do you want to setup any Kafka Connect connectors? (No), Number of Kafka broker nodes (3), Compute Family (m5.xlarge)</td></tr><tr><td>US East (Ohio)</td><td></td><td>Amazon RDS for MySQL</td><td>Storage for each RDS instance (General Purpose SSD (gp2)), Storage amount (50 GB), Quantity (1), Instance type (db.t4g.xlarge), Utilization (On-Demand only) (100 %Utilized/Month), Deployment option (Multi-AZ), Pricing strategy (OnDemand)</td></tr><tr><td>US East (Ohio)</td><td>storage</td><td>Amazon Elastic Block Store (EBS)</td><td>Number of volumes (1), Average duration each instance runs (730 hours per month), Storage amount per volume (3000 GB), Snapshot Frequency (Daily), Amount changed per snapshot (3 GB)</td></tr></tbody></table>

The below-given table gives infrastructure sizing for Production environment –

<table><thead><tr><th width="123">Region</th><th width="141">Description</th><th width="171">Service</th><th>Configuration Summary</th></tr></thead><tbody><tr><td>US East (Ohio)</td><td>BDB k8s cluster</td><td>Amazon EKS</td><td>Number of EKS Clusters (1</td></tr><tr><td>US East (Ohio)</td><td>worker nodes</td><td>Amazon EC2</td><td>Operating system (Linux), Quantity (4), Pricing strategy (On-Demand Instances), Storage amount (150 GB), Instance type (m6g.4xlarge</td></tr><tr><td>US East (Ohio)</td><td>Kafka</td><td>Amazon Managed Streaming for Apache Kafka (MSK)</td><td>Storage per Broker (1000 GB), DT Inbound: Not selected (0 TB per month), DT Outbound: Not selected (0 TB per month), DT Intra-Region: (0 TB per month), Data transfer cost (0), Do you want to setup any Kafka Connect connectors? (No), Number of Kafka broker nodes (3), Compute Family (m5.xlarge)</td></tr><tr><td>US East (Ohio)</td><td></td><td></td><td>Storage for each RDS instance (General Purpose SSD (gp2)), Storage amount (50 GB), Quantity (1), Instance type (db.t4g.xlarge), Utilization (On-Demand only) (100 %Utilized/Month), Deployment option (Multi-AZ), Pricing strategy (OnDemand)</td></tr><tr><td>US East (Ohio)</td><td>storage</td><td></td><td>Number of volumes (1), Average duration each instance runs (730 hours per month), Storage amount per volume (3000 GB), Snapshot Frequency (Daily), Amount changed per snapshot (3 GB)</td></tr></tbody></table>

<figure><img src="https://4072512490-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLFg37sm5677zgZ4m8et%2Fuploads%2FMElw8ns6d3PEYh9bmqhh%2Fimage.png?alt=media&amp;token=2b55ea1e-5d97-4443-bce1-77416a945111" alt=""><figcaption></figcaption></figure>

<figure><img src="https://4072512490-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLFg37sm5677zgZ4m8et%2Fuploads%2FVAqXJvMqWEmWO75KeAhw%2Fimage.png?alt=media&amp;token=6ae55e63-d1a0-40bf-97e0-7ad7d4b6a675" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
*<mark style="color:green;">Please Note:</mark> AWS Pricing Calculator provides only an estimate of your AWS fees and doesn't include any taxes that might apply. Your actual fees depend on a variety of factors, including your actual usage of AWS services.*    &#x20;
{% endhint %}

* [x] **Requirement**: Infrastructure sizing and technical deployment for each proposed data platform component Sandbox environmen&#x74;**.**
* [x] **BDB Response**: The below-given table provides infrastructure sizing for sandbox environment which can handle data ingestion of 500 GB to 1 TB daily.&#x20;

<table><thead><tr><th width="115">Region</th><th width="141">Description</th><th width="172">Service</th><th>Configuration Summary</th></tr></thead><tbody><tr><td>US East (Ohio<strong>)</strong></td><td>BDB k8s cluster</td><td>Amazon EKS</td><td>Number of EKS Clusters (1)</td></tr><tr><td>US East (Ohio)</td><td>worker nodes</td><td>Amazon EC2</td><td>Operating system (Linux), Quantity (4), Pricing strategy (On-Demand Instances), Storage amount (150 GB), Instance type (m6g.4xlarge)</td></tr><tr><td>US East (Ohio)</td><td>kafka</td><td>Amazon Managed Streaming for Apache Kafka (MSK)</td><td>Storage per Broker (1000 GB), DT Inbound: Not selected (0 TB per month), DT Outbound: Not selected (0 TB per month), DT Intra-Region: (0 TB per month), Data transfer cost (0), Do you want to setup any Kafka Connect connectors? (No), Number of Kafka broker nodes (3), Compute Family (m5.xlarge)</td></tr><tr><td>US East (Ohio)</td><td></td><td>Amazon RDS for MySQL</td><td>Storage for each RDS instance (General Purpose SSD (gp2)), Storage amount (50 GB), Quantity (1), Instance type (db.t4g.xlarge), Utilization (On-Demand only) (100 %Utilized/Month), Deployment option (Multi-AZ), Pricing strategy (OnDemand)</td></tr><tr><td>US East (Ohio)</td><td>storage</td><td>Amazon Elastic Block Store (EBS)</td><td>Number of volumes (1), Average duration each instance runs (730 hours per month), Storage amount per volume (3000 GB), Snapshot Frequency (Daily), Amount changed per snapshot (3 GB)</td></tr></tbody></table>

{% hint style="info" %} <mark style="color:green;">Please Note:</mark> AWS Pricing Calculator provides only an estimate of your AWS fees and doesn't include any taxes that might apply. Your actual fees depend on a variety of factors, including your actual usage of AWS services.
{% endhint %}