Short Coding Snippet

  Speed, scalability, productivity, and developer politics all played a role in AnyPresence’s selection of Node.js for its enterprise development platform A couple of years ago, the development team at AnyPresence was tasked with implementing a back-end server API generator for a large customer that wasn’t comfortable using Ruby on Rails in production and preferred an option in the Java ecosystem. To meet this requirement, the AnyPresence platform team invested a significant amount of time implementing a Java version of the generator in the Play framework. However, it was taking too long to implement features to match what was already available in the Rails version, so the team eventually started to look at alternative frameworks. That search ultimately led us to adopt Node.js and Sails.js, which is an MVC framework for Node.js. This article attempts to explain the reasoning behind these choices. roblem No. 1: Java, .Net, or Node.js? As an enterprise dev platform for Web,...

SQL Server still to this day deploys pessimistic concurrency out of the box. Anyone not aware of this “feature” starts out very disadvantaged on performance. This person will soon get an internet history filled with locking/blocking/deadlocking links. Postgres defaults to optimistic concurrency via its MVCC feature and is a joy to work with. Compression out of the box. With SQL Server, compression is an “Enterprise Edition and Up” feature which means you are spending the cost of at least 1 dev in order to get the ability to use compression. Once you have paid for that ability, you still have to figure out how to implement it. Postgres does this for you out of the box, automatically and for free. Concurrent Index Creation. You are going to find a recurring theme there…this is yet another feature that SQL Server is capable of doing, but only if you are able to afford the elite and affluent company of Enterprise Edition. Postgres has your back on this even if you left your wallet at home....

Download source code from GitHub   Table of Content What is distributed caching and its benefit IDistributedCache interface Framework provided to implement Distributed Redis cache Setting up Redis on Windows 10 Redis CLI commands Steps to integrate Redis cache in ASP.NET core Summary What is distributed caching and its benefit   Distributed caching is when you want to handle caching outside of your application. This also can be shared by one or more applications/servers. Distributed cache is application-specific; i.e., multiple cache providers support distributed caches. To implement distributed cache, we can use Redis and NCache. We will see about Redis cache in detail.   A distributed cache can improve the performance and scalability of an ASP.NET Core app, especially when the app is hosted by a cloud service or a server farm.   Benefits Data is consistent throughout multiple servers. This is more suitable for microservice architecture In case of loading balancing,...