Skip to main content

[Post Event] DevTalks 2016, Cluj-Napoca

This week we had another great conference in Cluj-Napoca - DevTalks. It seems that this month Cluj-Napoca is the hotspot of IT Conference in Transilvania. We have in only one month 4 conference with more than 500 attendees - what a crazy month.

At DevTalks Cluj-Napoca more than 600 people attended. There were 4 tracks in parallel, one of the track was 'Transition to 2020', where I was invited to talk about microservices. Because we will not have all the time the opportunity to write an application from scratch, I decided that the best topic is how to migrate a monolithic application to microservices. At the end of this post you can find my slide deck.

Title: How to migrate a Monolithic system to Microservices
Abstract: This is the story of how we need to change an existing monolithic system to be able to run over microservices. Lessons learned and best practices will be presented together with the most important architecture patterns that we need to take into account when we need to do such a migration. Migration is not a simple task, this is why it is important to learn from our past experience.



See you next year!

DevTalks 2016 Intro:
We’re kicking off a brand new edition of DevTalks. Bigger plans this year and a bigger interaction zone for you in Cluj.
The possibilities to gather under the same roof software developers & IT professionals are endless.The 2016 Dev Talks brings together great community leaders, innovation and fun, the key ingredients to explore the trends that will shape Mobile, Web, Big Data, Cloud Computing, smart devices, machine learning or AI. 
Coming soon in Cluj, on May 11th. Prepare for a paradigm shift, as Dev Talks 2016 in Cluj will take out new approaches in software development, highlighting its transition to 2020. Sessions on Machine Learning, AI&Robotics, IoT and wearables will be included in this year’s Agenda.

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 …

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…