Skip to main content

Azure blog post marathon is ready to start - December, 2014

By
Only one month remained from this year. I think that this is the best moment in a year to start a blog posts marathon.

Content
Day 1: Azure Redis Cache
Day 2: Azure CDN
Day 3: Azure Event Hub
Day 4: SQL Azure
Day 5: DocumentDB
Day 6: Azure Service Bus Topic
Day 7: Azure Traffic Manager
Day 8: Azure Express Route
Day 9: Azure Virtual Networks
Day 10: Azure Search
Day 11: Azure Scheduler
Day 12: Azure Active Directory
Day 13: Azure Machine Learning
Day 14: Azure Mobile Services
Day 15: Azure Virtual Machines
Day 16: Azure Media Services
Day 17: Azure Stream Analytics
Day 18: Azure Blob Storage
Day 19: Azure Table Storage
Day 20: Azure Queue Storage
Day 21: Azure File Storage
Day 22: Azure Cloud Services
Day 23: Azure Notification Hub
Day 24: Azure API Management
Day 25: Azure HDInsight
Day 26: Azure RemoteApp
Day 27: Azure StorSimple
Day 28: Azure Data Factory
Day 29: Azure Backup
Day 30: Azure Site Recovery
Day 31: Azure Multi-Factor Authentication

 So, what I have in mind?
Starting from December the 1st I will start a blog post marathon about Microsoft Azure. I will present the most important 31 services offered by Azure (from my perspective).
Each post will contain the following information:
  • Short Description
  • Main Features
  • Limitations
  • Applicable Use Cases
  • Code Sample
  • Pros and Cons
  • Pricing 
  • Conclusion


Are you ready? Then subscribe to this web feed. Together we will unlock the cloud power.


Labels:

Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too
Post a Comment
Read more