CodeProject Recently I got a chance to play little bit with .NET core on Linux where I developed an application in .Net core which I deployed on an Ubuntu 16.04 machine and configured to run it as a daemon process. In this process I learnt quite a few things which might be helpful for beginners in .NET core or for the folks who would like to play around with .NET core. Choosing the deployment model: Two types of deployments can be created for .NET core applications: Framework-dependent deployment: As the name implies, framework-dependent deployment (FDD) relies on a shared system-wide version of .NET Core to be present on the target machine. Because, .NET Core is already present, it can be shared by multiple applications hosted on the target machine. Self-contained deployment: Unlike FDD, a self-contained deployment does not rely on any shared components to be present on the target machine. All components, including both .NET Core libraries and the .NET Core runtime are includ
CodeProject Hello folks, In this post, we'll talk a little bit about Redis cluster. Limitations of Redis cluster. How we can overcome the limitations of redis cluster. Redis cluster is a distributed implementation of Redis with three major goals: High performance and linear scalability upto 1000 nodes. Acceptable degree of write safety. Availability: Redis cluster is able to survive partitions where the majority of the master nodes are reachable and there is at least one reachable slave for every master node that is no longer reachable. As an example, let's take a look at the following cluster configuration with six nodes. Node A (master node) Node B (master node) Node C (master node) Node D (slave of master node A) Node E (slave of master node B) Node F (slave of master node C) Now at this point, a natural question may arise, "When I write to a Redis key, how a node is picked up to store that key or what are the factors that decide which node to sto