Skip to main content

Why and Where for MongoDB, Cassandra, CouchDB, HBase, Membase, Redis

More and more people are starting to use NoSQL. I think this is extremely good. NoSQL can make our life better in a lot of situations. In this post I will try make a list of current NoSQL solutions that exist on the market and when we should use each other.

  • Dynamic query
  • Content is stored as documents
  • Big database that need to be very fast
  • Properties are stored like query and index
  • Can be used for voting system, CMS or comment storage

  • When you make a lot of updates and insert
  • Reading data is not the main scope of the database (writes are faster than reads)
  • Content is stored as column
  • High availability
  • Can be used with success for logging
  • Financial industry or any place where we work with a lot of data that is needed to be written
  • Basket of an e-commerce application

  • For data that don’t change very often (insert and read and NOT update)
  • We have a lot of predefined queries and we need versioning support
  • Is a great database for CMS and CRM.

  • When you do data analyzing
  • Works great in combination with Hadoop

  • When we need high concurrency
  • When the latency is very low and we want the latency to be minimal
  • Backend of a game or a system that offer data in real time

  • When we need to make a lot of updates
  • When the database is not too big and can be kept in memory
  • Can be used when we have a real time communication, for example a stock market with prices
If you know other NoSQL solutions or other strong points for this frameworks, please tell me.


  1. Nice...(1 word bez i want my comment also shorter and crisp like your post)


Post a Comment

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

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

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…