StackoverflowTips

 Copying All Blob of given Container into the same container and under subfolder? Here are few key points about the copying blob in Azure Storage Account: When you copy a blob within the same storage account, it's a synchronous operation.  When you copy across accounts it's an asynchronous operation. The source blob for a copy operation may be a block blob, an append blob, a page blob, or a snapshot. If the destination blob already exists, it must be of the same blob type as the source blob. An existing destination blob will be overwritten. The destination blob can't be modified while a copy operation is in progress. A destination blob can only have one outstanding copy operation. In other words, a blob can't be the destination for multiple pending copy operations. To copy a blob, call one of the following methods: StartCopyFromUri StartCopyFromUriAsync We are using  .Net Core 3.1 Step  1 :  Install-Package Azure.Storage.Blobs -Version 12.10.0 Step 2:  use ...

 When not to use microservices? Your defined domain is unclear or uncertain Improved efficiency isn’t guaranteed Application size is small or uncomplex Challenges of Microservices Microservices could be more expensive than monolithic applications. A poor design may lead to: Increased latency Reduced speed of calls across different services A cascading failure may overwhelm your server Poorly breaking down a module into microservices  Handling Distributed Transactions in the Microservice Running overproduction Disclaimer: following above screenshots from pluralsight.com

 What Are Application Deployment Strategies? An application deployment strategy is a way to upgrade an application with the new version of code. The aim is to make the changes without downtime in a way that the user barely notices the improvements. In this post, we are going to talk about the following strategies: Recreate : Version A is terminated and then version B is rolled out. Ramped (rolling-update/incremental): Version B is slowly rolled out and replacing version A. Blue/Green : Version B is released alongside version A, then the traffic is switched to version B.     A canary deployment consists of gradually shifting production traffic from version A to version B. Usually, the traffic is split based on weight. For example, 90 percent of the requests go to version A, 10 percent go to version B. Canary : Version B is released to a subset of users, then proceeds to a full rollout. A/B testing : Version B is released to a subset of users under specific conditions....