Operations | Monitoring | ITSM | DevOps | Cloud

.NET

Best 5 Tools for .NET Monitoring

.NET monitoring is a critical aspect of .NET application development. It helps developers track the health and well-being of their applications to provide real-time performance reviews. Knowing the real status of your application ensures that users have round-the-clock access to your business site. .NET monitoring makes sure that your business is not impacted by application issues. For example, problems experienced during site navigation can discourage customers from making a purchase from your site.

Getting Started with Azure Cosmos DB Using .NET SDK

Any application built today is expected to be highly responsive, highly available, and required to adapt to enormous changes in real-time at peak business hours, store ever-increasing volumes of data, and make that stored data available for users a fraction of seconds. To achieve such low latency and high availability, you need to deploy these applications’ Instances in data centers that are close to their users.

Logs and Traces: Two Houses Unalike in Dignity

Intelligent Medical Objects (IMO) and its clinical interface terminology form the foundation healthcare enterprises need, including effective management of Electronic Health Record (EMR) problem lists and accurate documentation. Over 4,500 hospitals and 500,000 physicians use IMO products on a daily basis. With Honeycomb, the engineering team at IMO was able to find hidden architectural issues that were previously obscured in their logs.

.NET Logging: Best Practices for your .NET Application

Logging is a key requirement of any production application. .NET Core offers support for outputting logs from your application. It delivers this capability through a middleware approach that makes use of the modular library design. Some of these libraries are already built and supported by Microsoft and can be installed via the NuGet package manager, but a third party or even custom extensions can also be used for your .NET logging.

Tanzu Tuesdays - Getting Started with Steeltoe and .NET Microservices with David Dieruf

If you are creating new .NET microservices for the cloud, modernizing existing applications for the cloud, or just plain moving apps to containers, Steeltoe is here to make things much easier. There is a list of things every microservice on a cloud platform should be good at. Unlike IIS on virtual machines an application running in a container is ephemeral - it could be run here today or there tomorrow. Microservices need to be resilient to this change but developers shouldn’t spend loads of time coding for this.

How Raygun increased transactions per second by 44% by removing Nginx

Here at Raygun, improving performance is baked into our culture. In a previous blog post, we showed how we achieved a 12% performance lift by migrating Raygun’s API to .NET Core 3.1. In publishing this, a question was asked on Twitter as to why we still use Nginx as a proxy to the Raygun API application. Our response was that we thought this was the recommended approach from Microsoft. It turns out this has not been the case since the release of .NET Core 2.1.

Get The Most Of Your .NET Builds With JFrog Artifactory

Give your DotNet ecosystem the full power of DevOps. The JFrog Platform covers the full application lifecycle of .NET builds from developer fingertips through distribution to consumers while covering application security, vulnerability analysis and artifact flow control. In this webinar will see how you can configure your .NET builds, so that they take full advantage of JFrog Platform for managing the lifecycle of your .NET artifacts.

Implementation of DevOps and Transformation of a .Net Framework to .NetCore for a Banking ISV

The client is a leading consulting company catering to Banking ERP Solution & ERPs for Sugar, Dairy & Spin Mills. With a proven track record of servicing to 150+ bank and credit societies in India, the client is looking to expand and enhance their offering which caters to financial institutions in India. CloudHedge suggested migration of .Net Framework to .NetCore and implement DevOps solutions to drive efficiency, high-quality code deployments, and scale at demand.
Sponsored Post

Achieving a 12% performance lift migrating Raygun's API to .NET Core 3.1

Here at Raygun, improving performance is baked into our culture. We don't just think about our application performance, but more broadly, we look at our own infrastructure and ask if there's anything we can do to make it more performant for our business and for our customers. Two years ago, we switched our API from Node.js to .NET Core and achieved a 2000% increase in throughput. To continue that story, we recently upgraded .NET Core 2.1 to 3.1 and saw a 12% increase in performance. We enjoy presenting our performance findings, so in this post, we'd like to give some context into why we upgraded and the conditions that helped us achieve the 12% performance lift.

Everything you need to know about .NET 5.0

If you’re a developer of .NET supporting enterprise apps developed in the .NET framework, you should know how the .NET 5 would impact your current enterprise app. Moving forward, there will be only one .NET to target macOS, Windows, Linux, iOS, Android, and more. Along with the release, there are new .NET APIs, language features, and runtime capabilities. The look and feel of the code and project files in .NET 5 would be the same, regardless of the type of app being created.