FPT SoftwareFHNCertificationsReference architectures
Talk to NGT
Platform Engineering · 03 of 6

Golden paths

From ticket queue to running service: four moves, a short form, one click, on EKS or EC2.

Golden Path: Ticket to Running Service
01

From ticket queue to running service

Template, short form, auto-provision, guardrails, deployed: minutes instead of weeks.

Golden Path: Ticket to Running Service
one clickThe ticket queue · weeksThe golden path · minutesBehind the short form · what the platform doesDeveloperneeds a serviceTicketReviewManual setupSecurityback-and-forthHand-wired pipelineWeeks laterPortalpick a templateShort formname · stack · envAuto-provisionrepo · IaC · pipelineGuardrails passscans · policy · costDeployeddev free · prod approvedObserveddashboards · tagsTemplatesPython · React · SpringCost estimatebefore it existsRepositorystandard layoutTerraformlanding zonePipeline seedor GitLab CITrivyscan · SBOMSonarQubequality gateArgo CDGitOpsGrafanametrics · logs

Point at a component to light its links; select it for what it does here and the practice that makes it right.

Point at a component to see what it does; select it for the best practice.Open the architecture
02

Scaffold, secure, build and test, deploy

Every golden path NGT builds follows four moves. The platform stops only at the gates you set.

  1. 01Scaffold
    • Repository from a template
    • App, IaC and pipeline seed
    • Dev container ready
    Builds on day one
  2. 02Secure
    • Single sign-on, role per environment
    • Secrets out of code
    • Policy as code
    Guardrails pass
  3. 03Build & test
    • Unit tests and code quality
    • Image scan, SBOM, signing
    • Security gate
    Quality & security gates
  4. 04Deploy
    • GitOps or pipeline to development
    • Promotion with approvals
    • Dashboards, alerts, cost tags
    Running, observed, cost-tracked
03

A new service from a short form

What a developer does, and what the platform does for them. Shown: a self-service form NGT built.

  • Pick a templateOne template per stack, such as Python, ReactJS or Spring Boot, on EKS or EC2.
  • Fill in a short formName, owner, runtime and environment. Everything else comes from defaults.
  • One click scaffoldsApplication code, Terraform and a pipeline seed are created together.
  • Gates on the first buildImage scan, code quality and an SBOM score; signed images in Harbor or Nexus.
A two-step self-service form in a developer portal: service name, description and a Create Service button
04

Two runtimes, one blessed path

Not every system is a microservice. Monoliths on virtual machines get a golden path too.

Microservices on EKSMonoliths on EC2
DeliveryGitOps with Argo CD and HelmJenkins with Ansible
ReleaseGitOps sync per environmentBlue-green with Auto Scaling groups and Systems Manager
ChecksTrivy, SonarQube, SBOM scoreThe same checks and gates
ObservabilityPrometheus, Grafana, Loki, TempoThe same stack
Local developmentDev containers, LocalStack, remote IDEThe same tooling
Paved, not walled.

A golden path is the easiest way to production, not the only way. Teams that step off it own what the path would have handled.

SourcesNGT Platform Engineering deck v1.2 (Sep 2026)NGT Platform Engineering Service Offering v1.0 (2025)NGT Service Offering v3.2 (Jul 2026)NGT Service Offering v2.0 (Mar 2025)NGT FinOps Service Offering (Mar 2025)