I have just tested Basic Azure MySQL Database and there is a bit confusion because of wording. I was wrongly assuming that it is a single database (similar to Azure SQL Database) but it is actually a server. That means you can have as many databases as you want to. So if anyone wants 1-3 single databases, it might be still expensive but if you have got multiple small not heavy traffic databases it might be convenient because of all other benefits on Azure platform.
I am using MySQL Workbench to connect to my databases. I get instant connection to my other remote (none Azure) databases but when I was connecting to Azure MySQL it took at least 5 seconds. I didn't test further but will see when I hook it to my websites.
Also agree with @MadsKristensen. All the projects I was working on so far you just want to bundle & minify as easy & quickly as possible and go. The new approach is much faster. Tried to play with gulp and finished questioning myself: "well it is interesting what you can do with gulp but all I only need is right click on css file and minify, or select a few css files and bundle them". I simply don't need to carry hundreds of files and play configuration game in gulp.
The way it is, just one json file is a clean approach and if you do need gulp/grunt you know what to do :)
It was helpful in a certain way. I still try to get my head around how my variety ASP.NET Core projects could benefit using Docker Containers. If they could at all.
I am using VMs where each of them has got a few websites and trying to learn when would be the good time to consider using Docker Containers, how much it would improve the deployment or whatever as I am quite happy even with the current form of deployment.
Or when there is not point to use Docker Containers at all. It's not right to force technologies if they are not needed but it is very good to know when they would be helpful.
That's why I mentioned my example. I could get Azure Windows Server 2016 VM with e.g. 4GB RAM and deploy there 10 websites and all is running well. Or I could get the same VM and deploy there my 10 websites to Docker Containers and now I don't know if 4GB RAM is going to be enough? Is this Docker deployment going to be more resources hungry or actually, I would be able to double amount of websites with no performance impact. Or shall I understand Docker Containers just as a new Binaries of deployment as you mentioned and so it will have no impact on the resources of the server at all?
And finally, the cost :) Would be the cost same using Docker Containers environment or cheaper?
Looking forward to watch this demo session to find out :)
What would be the real example of advantages using Docker Containers for hostingAsp.Net Core applications?
What would be the reason to move your current hypothetical Asp.Net Core applications running on a hypothetical regular Azure VM to the Docker Containers?
What about the performance? 10 Asp.Net Core applications running on a regular Azure VM (A) vs. the same 10 applications running in Docker Containers on the server with Containers with the same specs as (A).
Let's assume that the hypothetical applications are simple, not using any form of DB and all running on Windows platform.