cloud-native-toolkit / cloud-native-toolkit/planning

Andrea (the architect) wants a guide to provide an architectural POV for recommending tools to customer

Open
#684 0 comments 0 reactions 0 assignees View on GitHub
code pattern customer related documentation Persona: Architect
Dominant language
No language data
Stars
4
Forks
1
PR merge metrics
No merged PRs in 30d

Description

How do we have a conversation and position particular tools with customers? What is our opinionated view for a green-field environment (e.g. an environment that doesn't have a strong DevSecOps culture or is starting anew with cloud-native)? Where do we bend on certain tools and practices? Where do we not compromise on practices (and tools?)? How do we navigate an existing environment with a particularly opinionated customer?

The general framework is:

- Start with opinion around a platform
- Look at target workloads (cloud-native, app mod, integration, etc)
- Align with client's existing strategy
- Position upsell opportunities within the base open source tools

Some tools to consider for positioning:

- Ansible vs Terraform
- UrbanCode Deploy vs ArgoCD vs ACM?
- Artifact management tool (Artifactory, Nexus, etc)
- Image Registry
- Security Scanning

First we need a framework for how to evaluate these tools. What are the key features and capabilities we need? What are the considerations for security, scalability, resiliency and support?

Then we can provide some opinions around particular tools

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.