Skip to main content

[Post Event] DevTalks 2015, Cluj-Napoca

Today I had the opportunity to be one of the speakers of DevTalks conference. The conference was pretty interesting, with 4 different tracks in parallel (Web,  Mobile and IoT, Cloud and BI/BigData). From this perspective, attendees had a lot of options.
The thing that I liked at this conference was the subjects that were presented. It was not a conference only about a specific stack (only Java or Microsoft). Because of this, I decided to talk about cloud and to not take only Azure in consideration. I analysed all cloud providers that are on the market and I tried to expose what people should take into consideration where they are moving from on-premises to cloud.
Based on DevTalks website it seems that there were:
  • 416 attendees
  • 44 speakers
  • 40 presentations
  • 4 even stages (tracks)
There are a lot of "4" in this statistics. I hope that next year we will see "5" in their statistics.

Below you can find the slides and abstract of my presentation.
Title: What we should(n’t) know about cloud providers
Abstract: Nowadays, cloud is not only a trend, it is a solution that is recommended and used by everyone. This session is dedicated to all decision makers that are looking into cloud. We will take a look at the dark side of cloud and we will try to identify what are the things that we need to take into account before jumping in the world of cloud.
Slides:

Comments

Popular posts from this blog

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 …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.
publ…