Since I'd like to have the option of debugging my app on Docker for Desktop Kubernetes, I am trying to follow theses instructions in the book Kubernetes Up and Running 2nd Ed (KUAR) (page 181) to create a Reliable (Statefull) Singleton by creating a (1) persistent volume (2) a Pod that will run MySQL and (3) a service that will expose this pod to other containers.
Since I had trouble with MSSQL server on docker for desktop, I thought I would try postgresql or MySQL.
- If I were to use Azure SQL server instead of creating my own postreSQL or MySQL Kubernetes pod, would I still be able to run my app on my development destkop machine in Docker For Desktop/Kubernetes and have my web app connect to azure sql server from my desktop?
- I see that the KUAR book is creating an nfs-volume for maximum portability. Are there other options I should consider like azure-disks-dynamic-pv, azure-disk-volume or azure-nfs-volume that would work with PostgreSQL or MySQL? What might be the advantages?
- Let's assume that I am using just a tiny database to test my web app during development. I suspect using a nsf-volume, or azure-disk for PostgreSQL would be cheaper than a tiny database in Azure SQL Server. Is this true?
Thank you
Siegfried
Tue Nov 10 2020 Morning Update:
Ah! Connecting to that serverless database from SSMS on my development computer at home sounds good and I'd like to know (a lot!) more.
(1) Is Azure SQL the only candidate for serverless databases? While looking at the pricing calculator, I could not find the option for serverless MySQL or serverless PostgreSQL. If PostgreSQL & MySQL are options for serverless databases, please point me to the pricing calculator and the directions for creating them.
(2) I'd like to confirm that creating a tiny serverless SQL SVR database (1 MB data max) for development purposes will not cost me $528/mo for MS SQLSVR license fees. What defaults should I override to save money if I am not concerned about performance?
(3) I'd like to confirm that the pricing calculator for serverless (about $4.20/mo) includes the cost for the three steps of "az sql server create", "az sql server firewall create" and "az sql db create".
(4) I'd like to also confirm that after completing the those three steps and using the "--enable-public-network true" on the "az sql server create" step that I will be able to use SSMS or SQLCMD.EXE to manipulate the database in the absence of a kubernetess cluster with the port-forwarding feature (because I typically tear down my AKS clusters at the end of the work day to save money). If this is not true, please point me to the documentation to configure the proper network to use SSMS/SQLCMD on my home computer to access the serverless database. Please also confirm that I will be able to access this database from inside an AKS Cluster as well.
(5) Please explain the logic of having to "az sql server create" for a serverless database! This is confusing.
Fri Nov 20 2020 Update:
Another question: I thought there would be serverless cosmos available too but I could not find it in the pricing calculator. Did I miss it or does it not exist?
Tue Dec 8 2020 Morning Update:
This will be a tiny database containing sample data for developing a prototype web site (probably only a few megabytes) with some small simple queries a couple of times a day.
Fri Dec 11 2020 Update:
Let me retry rephrasing question #3. Please tell me about the charges for step 1 ("az sql create"). If this sits completely idle for couple of days, will there be any compute charges if there is no activity? I know from experience that there are significant daily compute charges for "az aks create" (with all the defaults) that sits completely idle for a couple of days. Apparently there are no compute charges for step 3 ("az sql db create") when this sits idle for a couple of days because this is the serverless part.
Thank you
Siegfried