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

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…