Skip to main content

[Post Event] Codecamp Cluj-Napoca, 2018

This weekend I participate at Codecamp Cluj and I was impressive of the event size. More than 1.000 people and 10 tracks in parallel. This free event it's now at another level from size and no of participants perspective. There were more then 50 speakers that delivered quality sessions about IT trends and trends. From AI to IoT and software processes to Java and .NET we had them all in Cluj-Napoca for one day.

Image may contain: 1 person, smiling, standing

At this event I had the oportunity to deliver to sessions about Azure Kubernetes Services and what quantum computer are preparing for the developers. You can find below slides and abstracts.

Title: Demystifying microservices inside Azure AKS
Abstract: The main purpose of this session is to put on the table things that we need to be aware of when we decide to run our .NET Core applications inside Azure Kubernetes Services. Microservices is powerful but comes with a new paradigm for how we need to design our applications and write our code. Join this session if you want to find more about it.
Slides:

Demystifying microservices inside Azure AKS Codecamp Radu Vunvulea 2018 from Radu Vunvulea

Title: Quantum programming in a nutshell
Abstract: I'm pretty sure that you already heard about quantum computers and how they will change the way how we do IT. In this session, we plan to take a look at the programming models that we need to use when we write applications for quantum processors. Sounds interesting? Then join this session for a journey in the world of quantum programming to find out how we should write code for this supercomputers.
Slides:

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