Prompt
I’m building reusable infrastructure modules for multiple app teams; what should I use?
Latest observation
Nov 7, 2026
OpenAI APIWeb search: off
For reusable infrastructure across multiple app teams, I’d generally recommend Terraform modules as the default choice.
Why Terraform modules
- Provider-agnostic IaC: works across AWS, Azure, GCP, and many others.
- Strong ecosystem: huge module registry, examples, and community support.
- Good abstraction level: lets you standardize patterns like VPCs, databases, IAM, Kubernetes add-ons, etc.
- Team-friendly: app teams can consume modules without owning the full underlying complexity.
- Reusable and versionable: you can publish, pin, and upgrade module versions safely.
Best practices for multi-team use
- Keep modules small and composable
- Expose only the inputs/outputs teams actually need
- Version modules with semantic versioning
- Add tests and CI validation
- Document examples for each common use case
- Enforce guardrails with policy checks if needed
When to consider something else
- Pulumi if your teams strongly prefer general-purpose languages like TypeScript/Python
- Crossplane if you want Kubernetes-style declarative infrastructure management
- CloudFormation/Bicep/ARM if you’re all-in on one cloud and want native tooling
- Platform engineering portal + templates if the goal is more “self-service golden paths” than raw modules
If you tell me your cloud/provider and whether your teams are more Kubernetes-native or Terraform-native, I can recommend a concrete module strategy and repo structure.