Skip to main content

ISTA Con 2015, November 18-19 - Sofia

Next month I am invited to participate as a speaker at ISTA Con 2015. This conference takes place in Sofia, Bulgaria. It seems that each year the conference is getting bigger and bigger. Last year there were more than 600 people that participated at the event.

A big difference between ISTA Con and other conferences is the number of tracks in parallel - there are 4 track in parallel and more than 30 speakers from 3 continents will speak.

 one. 
I'll talk about cloud and how to scale above clouds limits. We are living in era of cloud (Azure, Google, AWS) where scalability is not a real problem. Scalability may not be a real problem anymore. For having a good cloud solution you need more than 1.000 VMs and an ESB (Enterprise Service Bus). You need a healthy and reliable architecture.

See you at ISTA Con 2015, that will take place in Sofia (November 18-19, 2015).  

My session:
Title: How to scale above clouds limits 
Abstract: The number of devices that are online increases every day. The quantity of digital content that is produced every year sets new record each time. Last but not least clients are more and more demanding. A cloud provider offers us a great basket of resources but we need to know how to use and manage them. In this session we will talk about how to scale over this limits and how to be prepared for this kind of situations. If we are designing our system to be prepared to scale over cloud services limits then we will have a system that will be used in 5 year from now. We will talk about different scenarios when it is easy to reach different limits and we will learn how to overcome them.
  

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(

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

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too