Deploy NCache in Azure

Using Infrastructure as Code to Deploy NCache in Azure

Gone are the days when one of your servers crashed and you had to reconfigure it from the ground up. This would include a tedious, manual process from inspecting hardware malfunctions to software glitches. Now, organizations have adopted on-prem scripting tools to automate tasks and shifted the provisioning of IT infrastructure to cloud. However, this…

azure-service-fabric-ncache

Deploying NCache in Azure Service Fabric

Azure Service Fabric makes the deployment, management, and packaging of scalable and reliable microservice applications very easy and efficient. It simplifies the development and management of cloud applications as well as reliably scale and orchestrate services. Azure Service Fabric’s purpose is to provide developers with a very rich platform that addresses many of the problems…

Deploying NCache in Azure Kubernetes

Deploying NCache in Azure Kubernetes Service

Development, deployment, and management of applications has become easier with the introduction of containerization, which is why cloud deployment is gaining increasing popularity. Azure, being the best in the business, provides the fastest and easiest to use Kubernetes deployment in the form of Azure Kubernetes Service (AKS). To improve application’s performance in Azure Kubernetes environment,…

webinar-azure-cosmos-db

How to Use Caching with Azure Cosmos DB in NCache?

Cosmos DB is Microsoft’s new NoSQL store released in the Azure cloud. Unlike relational databases, it is scalable as it is a hosted database service, so it enjoys a lot of popularity among high transaction .NET and .NET Core applications. However, using Cosmos DB, you need to be wary of performance bottlenecks and cost overhead…

ASP.NET Output Cache in Microsoft Azure to Improve Performance

Microsoft ASP.NET Output Cache provides functionality to cache rendered content of ASP.NET pages or user controls for a specified duration. This allows your ASP.NET application to serve all subsequent requests from the cache instead of re-rendering and re-execution of a page. You add the <% @OutputCache %> directive on the page to use ASP.NET Output Cache.…