You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tool/README.md
+66-8Lines changed: 66 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Azure Databases Purview Tool - Unofficial
1
+
# Azure Databases Advisor Tool - Unofficial
2
2
3
3
Costa Rica
4
4
@@ -12,6 +12,31 @@ Last updated: 2025-06-20
12
12
> [!IMPORTANT]
13
13
> The information and code in this repository are provided for demonstration purposes only. For official guidance, support, or more detailed information, please refer to Microsoft's official documentation or contact Microsoft directly: [Microsoft Sales and Support](https://support.microsoft.com/contactus?ContactUsExperienceEntryPointAssetId=S.HP.SMC-HOME)
14
14
15
+
<details>
16
+
<summary><b>List of References</b> (Click to expand)</summary>
-[Microsoft Sales and Support](https://support.microsoft.com/contactus?ContactUsExperienceEntryPointAssetId=S.HP.SMC-HOME)
21
+
22
+
</details>
23
+
24
+
## Overview
25
+
26
+
The **Azure Databases Advisor Tool** is designed to help users select the most suitable Azure database service based on their specific use case. It provides recommendations by analyzing user inputs such as data type, scalability needs, latency requirements, and more.
27
+
28
+
This tool consists of:
29
+
-**Static Frontend**: A web-based interface for users to input their requirements and view recommendations.
30
+
-**Optional Backend**: A Flask API that processes user inputs and provides dynamic recommendations. The backend must be deployed separately to enable advanced functionality.
31
+
32
+
## Features
33
+
34
+
-**Interactive Questionnaire**: Users can answer detailed questions about their use case, including data volume, type, latency, scalability, and budget.
35
+
-**Dynamic Recommendations**: The tool suggests Azure database services such as Azure SQL Database, Cosmos DB, PostgreSQL, Synapse Analytics, and more.
36
+
-**Integration with Azure**: Designed to work seamlessly with Azure services and deployment models.
37
+
-**Customizable Backend**: The Flask API processes user inputs and provides tailored recommendations.
38
+
-**Static Web App**: A user-friendly frontend for interacting with the tool.
39
+
15
40
## Project Structure
16
41
17
42
```
@@ -26,15 +51,48 @@ tool/
26
51
27
52
## Usage
28
53
29
-
> This repository contains both a static web app and a backend API.
54
+
### Frontend
55
+
The static web app is deployed via Azure Static Web Apps or GitHub Pages. It provides an interactive form for users to input their requirements. By default, the frontend operates independently and uses hardcoded logic for recommendations.
56
+
57
+
### Backend (Optional)
58
+
The backend (Flask API) processes user inputs and generates recommendations dynamically. To enable backend functionality:
59
+
1. Deploy the Flask API (`app.py`) to Azure App Service or Azure Functions.
60
+
2. Update the backend URL in `script.js` to point to the deployed API.
61
+
62
+
### Deployment Instructions
63
+
64
+
#### Backend Deployment
65
+
1. Use Azure App Service or Azure Functions to deploy the Flask API (`app.py`).
66
+
2. Ensure the API endpoint is accessible to the frontend.
67
+
3. Use Azure Monitor for logging and diagnostics.
68
+
69
+
#### Frontend Deployment
70
+
1. Deploy the static web app (`index.html`, `script.js`, `styles.css`) to Azure Static Web Apps.
71
+
2. Update the backend URL in `script.js` to point to the deployed API (if using the backend).
72
+
73
+
#### Security
74
+
- Secure API endpoints with Azure Active Directory (AAD) authentication.
75
+
- Use HTTPS for all communications.
76
+
77
+
## Expanded Questionnaire
78
+
79
+
The tool now includes the following questions to refine recommendations:
80
+
-**Data Volume**: Expected size and growth.
81
+
-**Data Type**: Structured, semi-structured, or unstructured.
82
+
-**Performance Requirements**: Latency and throughput needs.
83
+
-**Scalability**: Horizontal or vertical scaling, global distribution.
84
+
-**Consistency Model**: Strong or eventual consistency.
85
+
-**Integration Needs**: Compatibility with Azure services.
86
+
-**Security and Compliance**: Encryption, role-based access control, compliance requirements.
87
+
-**Budget Constraints**: Monthly budget for database services.
88
+
-**Deployment Model**: Fully managed (PaaS), self-hosted (IaaS), or serverless.
89
+
-**Use Case Specifics**: OLTP, OLAP, or AI/ML workloads.
30
90
31
-
- The static web app is deployed via GitHub Pages.
32
-
- The backend (Flask API) is not deployed by default and must be deployed separately if you want to use it.
91
+
## Example Recommendation Flow
33
92
34
-
> [!NOTE]
35
-
> **If you want your frontend to use the backend API, you need to:**
0 commit comments