Skip to main content

TechEd 2013 - Pre-Conference Day

The pre-conference day of TechEd has finished. It was a full day with interesting seminars. For me, this morning was pretty hard to decide at what seminar I want to participate. I wasn’t decide what seminar to choose between “Enterprise Agility is Not an Oxymoron” and “Extending Your Apps and Infrastructure into the Cloud”.
In the end I decided to go to the second presentation, where I found out a lot of cool information related to this topic. In the next part of the post I will enumerate some interesting information that I discovered:

  • In this moment, most applications that are hosted on Windows Azure are ON AND OFF or PREDICTABLE BURSTING. To tell you the truth, I didn’t expected the ON AND OFF apps to be on top. 
  • Over 98% of organizations use and have virtualization. This is a huge opportunity for cloud providers.
  • Be aware of the SLA. If the provider cannot offer the uptime from SLA you will receive the money back for the downtime, but you will not recover the money that you lost during that period of time when your app or service is down.
  • You can find a SQL Server VM image on VM library that can be used on the cloud without having to buy your own license for SQL Server.
  • For VM you pay per minute and not per hour. First 5 minutes are free :-).

See you tomorrow night.

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

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

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