Hacker News Reader

Comment by SomaticPirate | Hacker News Reader

With this and Backstage it looks like there is a real need for a single pane of glass across an organization's infrastructure. From both a GUI perspective and an API perspective.

It looks like it would aid in more self-service and keep users away from cloud console's.

The workflow engine looks the most powerful since it would allow for a way to avoid fat fingering common manual changes.

Sad that it doesn't seem to offer any deployment visibility options. I would love to connect it to our CI/CD system to see what changes are currently being rolled out.

View on HN

Yeah definitely. A major pain point I've experienced recently is trying to figure out how to stand up various pieces of infrastructure needed to deploy my app at my company.

There's the k8s manifest, Cloudbuild config, various operators for databases, a CloudFormation repo for AWS resources, another one for Datadog config etc. It all feels very disjointed.

Does Helm help with any of this? I apologize if not, I just hear it used when these topics come up.

https://helm.sh/

You can deploy aws services (via cloudformation yaml) as a K8s manifest

You need none of that, and a single thick server on Debian will cover all your needs.

Monolithic architectures are more performant generally. That's the reason why we fly in giant aluminium tubes rather than by dangling off a flock of bird-sized drones.

Ah, efficiency vs. aesthetics is truly a perennial battle.

Checkout https://www.shuttleops.io/

It helps abstracting deployment away.

Disclaimer: I work @ ShuttleOps

> Sad that it doesn't seem to offer any deployment visibility options. I would love to connect it to our CI/CD system to see what changes are currently being rolled out.

Deployment visibility is what my startup - https://sleuth.io - is trying to focus on, with light workflow sprinkled in. Other options I've found are usually tracking as a side feature of a tool like Sentry, Rollbar, or GitHub, or a completely custom app like what Slack built in https://slack.engineering/deploys-at-slack-cd0d28c61701

I disagree. Working in IT infrastructure / DevOps for years theres nothing worse than maintaining aging infrastructure that was too tighly coupled or "too unified".

One job, one tool is still valid today.

Reply on news.ycombinator.com