When developing new applications, it’s typical to run into a variety of competitors with similar goals. This is one reason why it is not enough to create an application without ways to monitor and manage it. In fact, usually market leaders emerge rather quickly. So who are these market leaders?
Serverless technologies are lowering the barrier to entry for global deployments with on-demand pricing and scaling. AWS’ serverless offerings are now supported in 16 regions, and with the help of Up Pro’s latest v1.2.0 release we’re going to take a look at setting up a globally distributed app to decrease latency for your customers.
Slow websites are annoying, right? We sure think so. One common solution is to introduce a caching proxy like Varnish to help cache pages and reduce your server load. The good news is, if you have Oh Dear!, you can let those 2 work together.
Since it was first introduced in 2002, Microsoft’s .NET Framework has garnered a robust user base that includes organizations like UPS, Stack Overflow, and Jet.com. And now, thanks to the rise of the .NET Core runtime, this high-performance framework also supports cross-platform development. To provide deeper visibility into all of these environments, we are pleased to announce that Datadog APM and distributed tracing are generally available for .NET Framework and .NET Core applications.
This article is a follow up to Native Kubernetes Monitoring, Part One. In this chapter we’ll finish the two remaining demos for the other built-in tools, Probes and Horizontal Pod Autoscaler (HPA).
AWS CodeDeploy is a deployment management service offered by AWS. You can use it to deploy updates of your applications to your EC2 instances, Lambda functions, and on-premises servers. This can be a powerful tool in your CI/CD pipeline. Today, I’m happy to announce a new action: Deploy CodeDeploy Application.
New technologies often require changes in security practices. What is remarkable about containers and Kubernetes, is that they also provide the potential for enhancing and improve existing security practices. In this post, I will share a model that we use at Nirmata to help customers understand security concerns and plan Kubernetes implementations that are secure.
Amazon Elastic Container Service for Kubernetes, or Amazon EKS, is a hosted Kubernetes platform that is managed by AWS. Put another way, EKS is Kubernetes-as-a-service, with AWS hosting and managing the infrastructure needed to make your cluster highly available across multiple availability zones. EKS is distinct from Amazon Elastic Container Service (ECS), which is Amazon’s proprietary container orchestration service for running and managing Docker containers.
Working in C#, as with any language, you’ll soon find that that you need to do some debugging. With C#, thankfully, due to a plethora of debugging tools and techniques, troubleshooting is usually straightforward.
In Part 1 of this series, we looked at key metrics for tracking the performance and health of your EKS cluster. Recall that these EKS metrics fall into three general categories: Kubernetes cluster state metrics, resource metrics (at the node and container level), and AWS service metrics. In this post, we will go over methods for accessing these categories of metrics, broken down by where they are generated.
