Skip to main content

[Post Event] ITCamp Summer Community Event, August 18 - Cluj-Napoca

In August 18, 2016 we had IT Camp Summer Community Event in Cluj-Napoca. There were more than 55 people that attended to this event. In comparison with past events, we dedicated more time for networking between the sessions and at the end of the event.
There were two session in the afternnon. The first one was about .NET Security (including .NET Core) and the seccond one was about how we can write actor based concurrency using Elixir. Personally I discover a new word that Elixir has and is available for more than 30 years in Erland world. Seeing a system that has availability with 8 nines (99.99999) is something impressive, but thinking that such a system was availalbe 25 years ago is more impressive.
As usualy a big THANK YOU to all attendies and people that were involved behind the scene. And another THANK YOU to our sponsors that made this event possible:

Evozone
Recognos
You can find below the abstract to sessions and the slides from each of them. At the end of the post you can find pictures from the event.

See you next time!

.NET Security (Radu Vunvulea)
Abstract: When is the last time when you pushed an update to .NET framework in a production environment? Did you define an updated process of .NET framework for production environments? Is the support team aware about what can happen if a security update is not pushed to the machines? 
In this session we will take a look on some security problems that .NET framework has and what can happen if we don't take security into account. We will take a look on different versions of .NET (including .NET Core). Best practives related to this topic will be covered and debated.
Slides:

Actor based concurrency with Elixir
Abstract: Because of increased demand for interconnected systems(IOT, SAAS) we need new improved ways of handling reliable (soft)real-time systems. One battle-tested approach is based on the Actor Model pioneered by Erlang and brought to the masses by Elixir.
Topics that will be covered:
- short introduction to functional programming principles with examples in Elixir
- actor model concurrency: why is it needed, advantages & disadvantages
- OTP patterns for handling agents: GenServer & Supervisor

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