Back to Tech landscape

NGINX

Cloud & DevOps

Reverse proxy and edge routing

Official documentation (opens in a new tab)

Overview

NGINX fronts services in Kubernetes ingress and static hosting patterns; YARP covers in-process .NET reverse proxy scenarios.

Microsoft Azure is our primary cloud: Factory templates deploy to App Service, AKS, Container Apps, and managed data services with Bicep or Pulumi, Azure DevOps pipelines, and Application Insights baked in from day one.

When engagements require hybrid or multi-cloud tooling, we adopt it with explicit landing zones, least-privilege identities, and runbooks—while keeping Azure the anchor for ConnectSoft-generated platforms.

From first commit to production dashboards, our DevOps path favors repeatable infrastructure, managed identities, and measurable SLOs—so releases stay boring in the best way.

Why we use it:

  • Ingress controller on AKS
  • TLS and rate limits
  • Static file offload
  • Health-checked upstreams
  • Infrastructure as code with environment-specific parameters
  • Managed identities and private networking in production paths
  • Integrated CI/CD through Azure DevOps and quality gates

Ready to work with us?

Let's discuss how our team can help achieve your digital goals