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

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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...