Skip to main content

TechEd 2013 - Day 4

Last day of TechEd 2013 ended, goodbye Spain. This day ended with a lot of interesting sessions related to Windows 8, Azure and Big data. I discover new ways how we can use Bitlocker for enterprise customers and why different 3rd party prefer to use Bitlocker and give up of their own mechanism.
I think that you heard that the preview version of Windows 8.1 can be downloaded from Microsoft news. Be aware, if you install the preview version of Windows 8.1, moving to the final version of 8.1 will not be so easily. When you go to the preview version, don’t let the installer to update the backup partition also. In this way it will be very easily to go back to 8.0 and install the final version of Windows 8.1. In general I prefer to use install the preview version of any software o virtual machines.
While attending to a session about big data and Hadoop I find out how you can increase the performance of a reduce operation. During the reduce operation it is recommended to have as few as possible. Even if the size of the files is big, it is not important. Having only a few number of files at this step will make the reduce operation faster.
“ASVMITI” is the storage mechanism offered by Microsoft. One of the benefits of this storage is the persistence. The SLA that is offered to the clients will offer us the data persistence and access of all information, even if we will stop or delete our HD. This is great, because after the process of data ends, we will be able to access all this data. Don’t forget that storing data into cloud is very cheap. As input, we can use any kind of data, even archives of type gzip, bz2 or deflate.
The last 5 posts were only a small summary of things that were presents at TechEd Europe. A lot of interesting news and information was shared at TechEd. All the sessions can be viewed on Channel 9.

Comments

Popular posts from this blog

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

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(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP