[Post Event] Cloud Conference 2018, Bucharest

Today (April 19th, 2018) I had the great opportunity to be invited as a speaker at "Conferinta de Cloud." I was amazed to find out that around 300 people join this event, that it is dedicated to cloud and Microsoft Azure.
The event has two tracks, one dedicated to the business side and a second one dedicated to technical one. I was surprised to discover that almost half of them were interested in the business track. This is a good indicator that confirms us that cloud is here to stay and Microsoft Azure it is used more and [more in business.

I delivered a session focused on things that we need to take into account at the moment when we start a project on the cloud. People forget to check the most basic things when they kick-off the project. Because of this, they are ending in situations where the consumption is over the limits or data is public accessible.

Session slides can be found below:
Title: Day Zero In A Cloud Project
Abstract: In this session, we will take a look at what we need to keep on our radar when we start a new project inside the cloud. When not only us but also clients are new in cloud ecosystem, we need to be aware of small things that can make a difference or secure the success of the project. Things like security, environment isolation and access controls are just a tiny part of the things that we need be aware. There will be examples from real life projects and hands-on implementations inside Microsoft Azure. After joining this session, you will have an initial view on what things we shall be aware when we start a new project inside the cloud.

Slides:

Day Zero in a Cloud Project | Radu VUnvulea from Radu Vunvulea

Comments

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(

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

Navigating Cloud Strategy after Azure Central US Region Outage

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

Cloud as a Story - Vunvulea Radu

Search This Blog