Tag: .NET

The Microsoft on AWS Cost Optimization (MACO) recommendation guide is a collection of cost optimization strategies designed to help you optimize both new and existing Microsoft workloads on Amazon Web Services (AWS). It offers foundational training, cost optimization techniques, and reference architectures to build and automate cost-effective, high-performing workloads that meet business objectives. The MACO […]

In this blog post, I will show you how to use the myApplications dashboard in the AWS Management Console. Using a sample .NET application, I will demonstrate how you can manage costs, monitor, and optimize your Microsoft workloads with this new dashboard. Introduction Assume you are a web application owner and it’s your team’s responsibility […]

With Amazon Web Services (AWS), you have three main types of compute to choose from: instances, containers, and function-as-a-service. While all of them can be used to host .NET applications, choosing the right type can help you achieve the best possible architecture for your application. In this blog post, I review a few common types […]

Celebrating 15 years of running Microsoft workloads in the cloud, longer than any other major cloud provider Before we wrap up 2023, I wanted to capture some of the highlights of the year—so I reached out to my esteemed colleague, Rajesh Rathod. Rajesh is an Amazon Elastic Cloud Compute (Amazon EC2) product leader who has […]

A brief history of .NET In 2002, Microsoft introduced .NET Framework as a software platform for Windows to help developers rapidly create business applications and simplify complex programming tasks. Thousands of organizations of all sizes began to use it to create software for their business models. Millions of developers around the globe adopted .NET Framework. […]

In this blog post, we will show you how to create a documentation solution on the Amazon Web Services (AWS) Cloud that automatically generates and publishes a technical documentation website for a .NET project, based on source code comments, API definitions, and Markdown documents included in the project. Having a technical documentation website improves developer […]

Building a well-architected .NET application goes beyond just coding and deploying. You must monitor performance, trace transactions, collect logs, gather metrics, and trigger alarms when metrics breach thresholds. To achieve this, you can design and implement telemetry to enable observability capabilities. In the first part of this blog series, I covered the implementation of metrics. […]

Building a well-architected .NET application goes beyond just coding and deploying. You must monitor performance, trace transactions, collect logs, gather metrics, and trigger alarms when metrics breach thresholds. To achieve this, you can design and implement telemetry to enable observability capabilities. In the first post of the series, I covered the implementation of metrics, and […]

Building a well-architected .NET application goes beyond just coding and deploying. You must monitor performance, trace transactions, collect logs, gather metrics, and trigger alarms when metrics breach thresholds. To achieve this, you can design and implement telemetry to enable observability capabilities. This post is the first in a series of three posts in which I […]

CDK offers a high-level abstraction to define AWS resources using modern programming languages. Among its components, it provides aws-s3-assets, which is a high level construct that abstracts packaging AWS Lambda functions. The default behavior of this construct is to zip all the content into a folder and upload it to an Amazon Simple Storage Service (Amazon S3) bucket. That works great for Lambda runtimes like Python or Node.js, which do not require code compilation, but for .NET, Java, or Go, which requires code compilation, you’ll need extra steps to restore external dependencies, compile the code, and publish the binary. This post will explore how to streamline building, packaging, and publishing .NET Lambda functions using AWS CDK.