Archive for the ‘Microsoft Azure’ Category

During the last BUILD 2014, Microsoft has released few updates on Azure, one of them was the latest SDK (software development kit) for developing on it. The main new updates are mainly around the different capabilities you can do through your Visual Studio, like for example creating new Virtual Machines directly from the VS. To do so you have to open your visual Studio and open Server Explorer, you will find one the available drop downs, Windows Azure, connect to your azure account by right clicking on Windows Azure then click on “Connect to Windows Azure” and sign in easily.

If you go to Virtual Machine and you right click on it, choose “Create a Virtual Machine“, you will get a wizard, where the first step is where you can choose which Azure Subscription you will be choose. After that you will follow the normal steps like creating a Microsoft Azure Virtual Machine from the portal.

Choosing the Virtual Machine OS:

Select the Machine Settings:

Select the Cloud Service you want the VM to join:

At the end, customizing the VM Endpoints as you need:

TADA! Now you can create the Virtual Machine directly from your VS.

The second feature that was added to the SDK, is that you can directly connect to your Microsoft Azure Virtual Machines or websites to directly and easily publish the new content without the usual hassle of debugging and uploading the different content of application. You can find all the details and see the different ways to debug a VM or a Website, publish new application through this MSDN link.

I also liked a new way of sending the notification to your device applications, which you can also find in the server explorer node, under the Windows Azure, the “Notification Hub“. You can also find the link here, on how to do that.

Advertisements

Like the same introduction for the Microsoft Azure
CDN, maybe it will be nearly the same for the Microsoft Azure Cache. The network regulation for an IT infrastructure, a better way for sending the content for the end users. If you are dealing with basic websites or HTTP protocols, the Microsoft Azure Cache Service will be the perfect match for you.

Well yes the Microsoft Cache is still in preview, however I will go to some features that might be helpful. The Microsoft Azure Cache Service is a very useful solution for building an accelerated high scalable application, there are several ways to so, based on the MSDN page there are around 3 ways to do so, one is through the Microsoft Azure Portal, you will find the Cache Service in one of the services at the left most of the page, you just need to scroll down. Or you can do the caching service through the In-Role Caching, through your Cloud Service, whether through the WebRole or even the WorkerRole and the third way is through the Sharing Cache Service, I won’t be covering this one as it will retire soon.

So to do the Microsoft Azure Caching service through the portal you will have to go to the Portal and scroll down until you find the cache Service.

Or you can go directly to the Data Services, you will find the “Cache -> Quick Create -> Continue the configuration”

cache configuration

So as normal for the region you will have to choose the nearest place to your target customers, after that we will have few Cache offerings:

  • Basic 128MB to 1GB
  • Standard 1GB to 10GB
  • Premium 5GB to 150GB

After that you can find the cache memory and you will choose what best suits you based on the cache offering chosen.

The other way the In-Role Cache, is a way to cache your data in a previously created, running role whether it was a WebRole or a WorkerRole, you can do so simply by modifying the Role Configuration file (which is ServiceConfigurationSetting) and the Client Configuration file (which is the web.config). You can do so following the instructions from the following link. In this case you don’t need anything from the caching service on the portal just you need to know and understand the capacity planning.

A new feature of Microsoft Azure has been released on the last April 2nd, not quite a very new one, but an updated one. If you are familiar with the CDN or the content Delivery network from previous engagement with Microsoft Azure than you will be certainly aware what it is about.

The CDN stands for content Delivery network, it is like a dummy datacenter that acts only for delivering the content to the customers. With the growth of the internet usage and the also the increasing number of the Cloud Consumers, the datacenter no matter how strong was its network infrastructure cannot process all the incoming requests so what really happens is, that the Microsoft CDN is mainly used for caching the Microsoft Unstructured storage (BLOB) and the static content used by the Cloud Service
(like mentioned in the MSDN page). Their main target is to deliver the content to the target customers in an easy and more effective way. You can check the locations of the latest Microsoft Azure CDNs locations, so for example if you do have an application hosted on Microsoft Azure, you can put your data (BLOB storage) or your web role (Cloud Service) in the nearest place for your customers to better serve them.

So how to work with Microsoft Azure CDN?

First thing go to your portal and go down until you find the CDN tab

Or you can directly create it by pressing “New -> app Services -> CDN -> Quick Create”, now you create CDN based on your previously created Azure Storage account or based on a Cloud Service previously created.

PS: if you choose to create a new CDN based on your storage account, you will find the origin domain will be “accountstoragedomain.blob.core.windows.net“. If you created based on your Cloud Service, the origin domain will be “CloudService.cloudapp.net“.

After you click the create button, you will be able to see the CDN that has been created for you in few seconds. Once you open the CDN you have created you can see all the configuration that are working on your CDN, so let me get to the CDN tabs at the bottom of the page.

What I really want go through is the manage domains, you can get you own customized domains and subdomains to map the exiting CDN domains.

 

To work more on Microsoft Azure CDN and to learn more about hosting Websites on Azure CDN, kindly follow this link.