How Intuit’s Platform Engineering Team Chose an App Definition

2 years ago thenewstack.io

Summary: This is a summary of an article originally published by The New Stack. Read the full original article here →

DETROIT — When Intuit’s platform engineering team set out to choose an application definition, it ultimately decided it required a data-centric approach. With too many tools to evaluate, including the prospect of building its own in-house, it settled on four open source possibilities: https://helm.sh/, https://kustomize.io/, https://kubevela.io/ and https://github.com/crossplane/crossplane.

But that created a number of problems: No. 1 — Kubernetes and cloud complexities are exposed directly to application developers.

No. 3 — Lack of operational input in the application definition, things like how do I enable high availability in my service using an application definition?

“We wanted a desired target state where application developer specifies the application intent.

DevOps Articles