Skip to main content

Eveniment: Mobile in the Cloud (13 octombrie - Sibiu, 8 noiembrie - Cluj-Napoca)

iQuest v-a pregătit 2 eveniment extrem de interesante, unde urmează sa țin și eu o prezentare. Sa nu ratați prezentarea lui Bernd Kullick care se anunța extrem de interesanta. Intrarea este libera. Va așteptam pe toți!
Interesat să ții pasul cu cea mai nouă tehnologie și să afli tot ce e nou de la specialiștii cu experiență?
Pe 13 octombrie la Centrul de afaceri Sibiu și pe 8 noiembrie la Hotel City Plaza Cluj-Napoca ai oportunitatea de a participa la evenimentul Mobile in the Cloud, un eveniment marca iQuest cu sprijinul Microsoft. Vei afla cele mai noi informații despre tehnologiile de cloud și mobile development de la profesioniștii care lucrează la probabil cel mai mare proiect de Cloud din Europa.
Programul pe care ți-l propunem este:
9.00 – 9.30 – Registration & Welcome coffee
9.30 – 9.45 – Keynote
9.45 – 10.15 – Introduction in Microsoft Windows Azure cloud platform, Zoli Herczeg, Evangelist, Microsoft
10.15 – 10.45 – Azure project showcase: EyeOnEarth, Bernd Kullick, Senior Consultant – Windows® Azure, Microsoft Services Germany
10.45 – 11.00 – Coffee break
11.00 – 11.30 – Development of cloud connected Smartphone Applications, Petru Jucovschi, Evangelist, Microsoft
11.30 – 12.30 – Sudoku7: A Windows Phone 7 and Azure Development Experience, Radu Vunvulea, iQuest
12.30 – lunch
La Sibiu, evenimentul se va desfasura in sala de conferinta din corpul A, etajul 2, al cladirii Centrul de Afaceri Sibiu, iar la Cluj-Napoca, locatia este sala Ballroom a hotelului City Plaza Cluj. Detalii suplimentare si update-uri se gasesc pe pagina dedicata evenimentului www.iquest.ro/mobileinthecloud .
Participarea este LIBERÄ‚, în limita locurilor disponibile – rezervaÈ›i-vă chiar acum unul pentru Mobile in the Cloud!
Ne vedem acolo!

Comments

  1. Ne-am vazut, si a fost ok. Bafta in continuare in Cluj, fara emotii ca e foarte bine ce ai facut.

    ReplyDelete

Post a Comment

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