Ok, I have to admit that when I login into my Azure Portal and it seems like a long time since I meddle around with the new technologies that is being released by Microsoft.
I have heard a little about the power of Azure Cosmos DB but have not really played with it yet! I would like to take the chance to run through it and blog down my learning!
Navigate through Azure Marketplace, go to “Databases” and you will be presented with the different offering of Database options. I went ahead to select “Azure Cosmos DB” as shown.
There are multiple API data model offerings in the Azure Cosmos DB. Some of the examples are as followed:
For an introduction to the respective data model, you may navigate to the following site:
After the deployment process has been completed, you will be able to find that under your Resources within the Azure Portal.
As you can see, there is more than just .NET platform that is being supported as part of this Cosmos DB and for now, it is just waiting on creating the item collections before able to consume the Cosmos DB.
I am pleased with the way how the getting started is going and it is relatively easy for any Azure Administrator to spin up new Cosmos DB.
In the next posts, I am going to walk through deeper into how I am using Cosmos DB and storing data into it.
I have to admit that I am no longer one who is managing a production environment since my primary focus is to bring in more customers into the organization. One simple yet cool feature of upsizing in Microsoft Azure that Microsoft has designed really amazed me and bring me to the thoughts that how importance is User Experience.
Take for example, what if one needs to scale up the instance size of Azure Virtual Machine (VM), how many steps to accomplish that?
Step 1 – Navigate to the instance and look for the one that you intend to scale up and select the “Size” as shown below.
Step 2 – Select your desire configuration based on your requirements and the pricing model which is stated clearly.
Step 3 – Once confirm, the instance will be required to reboot and the resources will be upgraded shortly.
Is this kind of features notice by everyone or most just take it as it should be? I personally feel that within the Product Group of Microsoft, they take into consideration of the views and opinions of the Public User and have them implemented into the environment as soon as possible.
For this, let’s give a hands-up to Microsoft!
Today when I was meddling with my Virtual Machine (VM) in Microsoft Azure, I chanced upon this new feature known as “Auto-shutdown” under the section “Schedules” although this was originally released in November 2016. The piece of news can be found here. With this naming, it tells it all that Microsoft is helping us consumers to save some costs! (Thanks Microsoft!) #MicrosoftIsGreat.
Clicking on it further brings me into this simple form.
As you can see that this form is rather simple to operate which also means that it is missing some features that I can think off immediately upon seeing this.
Microsoft Azure team has built this feature to allow you to shut down at anytime at your convenience which is down right the whole purpose of this. I faced with tons of issues with time zone where I set an alarm at 6pm (GMT +7) and after a flight, it does rang only at the specified time zone even I return to my home land which is in (GMT +8).
One of the immediate limitation of this is, once you scheduled a time to have the resource to be shut down. It will be on run on a daily basis, which means that I will need to manually start the Virtual Machine if I need to. Well, a list of awesome features that I hope to see on this Schedules will be:
1) Auto-StartUp – Automatically start the resource if it is not in the Stopped State at a specified time.
2) Allow more granular control such as:
- Control by Shutting down on a specified day of the week/month
- Control by Starting up on a specified day of the week/month
3) What is better is, if I can even start/stop a resource by using my Mobile Device (regardless of Email/Mobile Application)