Skip to main content

Less than 1 week until Microsoft Ignite 2017

First time when I took part at Microsoft TechEd in 2012 in Amsterdam. It was one of my first conferences with more than 5k attendees. It was a wow, from all perspective. From then I participate to each TechEd and Microsoft Ignite.
At Microsoft Ignite, attendees have the opportunity not only to learn and discover new stuff, but also to meet people all around the globe. It is that week in the year when you can meet face to face Program Managers from Microsoft together with people that you talk over Twitter from Japan, Australia, UK and USA in only one place.

This year things will be a little different. It will be the first time when I participate at Microsoft Ignite not as attendee, but also as speaker. It is a joy to be invited to speak at a conference with more than 23000 attendees. If this is not enough, I will have 3 sessions where I will share my knowledge and experience related to IoT, security and NoSQL. If you want to find more about this subjects feel free to join my sessions - https://myignite.microsoft.com/speaker/225150 

Even if you are joining my session or not, if you are coming to Microsoft Ignite, give me a ping and let us meet and have a talk.

Here’s more you can expect from Microsoft Ignite:

  • Go in depth with over 40 pre-day sessions to choose from, including Microsoft Azure, SharePoint, Dynamics 365, Windows, and much more
  • Learn about the future of tech in Microsoft CEO Satya Nadella’s keynote
  • Meet up with colleagues, view sessions, and discuss what you’re learning in the Hang Out
  • Gain insights from industry leaders with Women in Business and Tech programming


See you next week in Orlando!

Below you can find the list of sessions that I will have at Microsoft Ignite.
Enterprise security in practice
How does an enterprise look when you talk about security and cloud? Complicated, rigid, and difficulty accepting cloud-based architectures. After working closely with security teams from different companies, we've identified different approaches and requirements that are standard for enterprises. In this session, let's discuss and share lessons learned on how we can map security requirements to Microsoft Azure.

Power-up NoSQL with Azure Cosmos DB
NoSQL databases are here to stay. Extremely powerful and flexible NoSQL solutions improve our systems and have a direct impact on our business. Common discussions when you are using NoSQL solutions like DocumentDB or MongoDB are disaster recovery plans, backups, scalability, replication, clustering, security and many more. What if I told you a successful story on how we reduced all these topics to only one - Cosmos DB. Join this session if you want to find out how we deployed a worldwide NoSQL solution using Azure Cosmos DB.

The story of an IoT solution
Yes, this is a session about an IoT platform, within a challenging environment. Four years ago I was deeply involved in the creation of an enterprise grade IoT platform. Guess what, Microsoft came up each year with new services and products to the market that changed the shape of our platform. The session tells the architecture story of the platform and covers the most important points in time. See how we integrated Azure Event Hubs, IoT Hub, Microsoft Power BI, Azure Data Lake, and Azure Cosmos DB in an agile manner integrating ARM and other Microsoft technologies, products or services.

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