Skip to main content

[Community Event] Event Sourcing and CQRS | ITCamp Community Summer Lunch Event in Cluj

At the end of this month (July 24) we will have a special guest in Cluj-Napoca: Andrea Saltarello. The format of the event will be different from the previous ones. The event will take place during the lunch break at The Office and is free.
If you want to find more about the event you can check the following registration links. See you at the event.

Meetup: https://www.meetup.com/ITCamp-Community/events/241394189/
Eventbrite: https://www.eventbrite.com/e/event-sourcing-and-cqrs-itcamp-community-summer-lunch-event-in-cluj-tickets-35994003032
ITCamp Community blog: https://community.itcamp.ro/2017/07/itcamp-community-summer-lunch-event-cluj-event-sourcing-cqrs/

Official announcement:
Let's try a different kind of event this summer. I proposed to all of you to meet during the lunch break and have a talk about Event Sourcing and CQRS. There will be a special guest (Andrea Saltarello - Solution Architect at Managed Design) that will talk about his own experience on how we should manage Event Sourcing.
If you want to join this talk, then you should book it in your calendar. Don't forget that the event is free being supported by our local community sponsors: 8x8 and Yonder.
When: July 24
Where: The Office , Room A (ground floor)
Agenda:

  • 12:15 - 12:30 | Networking
  • 12:30 - 13:20 | Azure Tales: a real world CQRS and ES Deep Dive (Andrea Saltarello)
  • 13:20 - 13:50 | Networking and sharing experience

Title: Azure Tales: a real world CQRS and ES Deep Dive
Description: Both CQRS and Event Sourcing are by no means the new kids on the block anymore, yet a lot can be told about how to use Azure’s PaaS to implement such patterns and unleash their power without having your costs soaring. The ingredients are: CosmosDB/MongoDB as the event storage, Service Bus as the events’ dispatcher, AppServices/Cloud Services/Service Fabric as the scalable, fault tolerant code cruncher, SQL Azure as the read model and ASP .NET Core as the application framework used to implement views and back-end services. Eager to know the recipe (and look at real code)? Don’t miss this talk then.
Speaker: Andrea Saltarello (Solution Architect | MANAGED DESIGNS)
Bio: Andrea Saltarello is CEO and founder of Managed Designs, a company providing consultancy services related to software design and development. A solution architect, Andrea is still eager to write code in real projects in order to get feedback about his architectural decisions; he is co-author of “Microsoft .NET: Architecting Applications for the Enterprise” by Microsoft Press: first released in 2008, the second edition hit the stores in September 2014. As a trainer and speaker, Andrea had several speaking engagements for courses and conferences across Europe such as DevWeek and Tech-Ed Europe; he also taught “Operating Systems” during the “Master in Editoria Multimediale” class organized by the University “Politecnico of Milan”. In 2001 Andrea co-founded UGIdotNET, the first Italian .NET User Group of whom he is the President and leader: due to his community efforts, he has been granted the Microsoft MVP award since 2003.



A BIG THANK YOU for our local community sponsors that made this event possible:

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