Alok Notes

  Cognitive search and Elastic search Azure Cognitive Search :-  The Azure Cognitive Search service enables search over different types of content by letting you create and manage search indexes. You can import data from a variety of sources, with AI-powered indexing that can infer and extract searchable content from non-text sources. You decide what data is imported into the index, and set up indexers to pull that data into it, or push JSON formatted documents manually. Azure Cognitive Search also lets you query search indexes. The results contain only your data, which can include text inferred or extracted from images, or new entities and key phrases detection through text analytics. It's a Platform as a Service (PaaS) so Microsoft manages the infrastructure and availability, allowing your organization to benefit without the need to purchase or manage additional hardware resources. Azure Cognitive Search exists to compliment existing technologies and provides a programmable searc

TLS 1.0 is a security protocol first defined in 1999 for establishing encryption channels over computer networks.  Microsoft has supported this protocol since Windows XP/Server 2003.  While no longer the default security protocol in use by modern OSes, TLS 1.0 is still supported for backwards compatibility.  Evolving regulatory requirements as well as new security vulnerabilities in TLS 1.0 provide corporations with the incentive to disable TLS 1.0 entirely.  TLS 1.2 is a standard that provides security improvements over previous versions. TLS 1.2 will eventually be replaced by the newest released standard TLS 1.3 which is faster and has improved security.   To ensure .NET Framework applications remain secure, the TLS version should  not  be hardcoded. .NET Framework applications should use the TLS version the operating system (OS) supports. With TLS 1.2/1.3 change impact the source code uses the following namespace/library/classes. Directly using the  System.Net  APIs (for example,  S

Azure Load Balancer Azure Load Balancer allows us to scale our applications and create highly available services. Azure load balancer allows you to distribute traffic to your backend virtual machines. An Azure load balancer provides high availability for your application. The Azure load balancer is a fully managed service itself. Azure Load Balancer includes a few key components. These components can be configured in your subscription through the Azure portal, Azure CLI, Azure PowerShell, Resource Manager Templates or appropriate alternatives. Following components play and important role in working of Azure Load Balancer. These are Frontend IP configuration The IP address of your Azure Load Balancer. It's the point of contact for clients. These IP addresses can be either: Public IP Address Private IP Address The nature of the IP address determines the type of load balancer created. Private IP address selection creates an internal load balancer. Public IP address selection crea