9 ms·
this works for them because there's a close mapping between the code and the infra it needs. For the more general case of IaC, it usually benefits greatly to be
by arccy 5y ago
this works for them because there's a close mapping between the code and the infra it needs. For the more general case of IaC, it usually benefits greatly to being closer to data rather than code, allowing a wider range of tools to work with/process it over long term maintenance.
- tholm 5y agoThat's the intent. This approach doesn't preclude the need for underlying IaC (DSL or programmatic). The idea here is to allow an application to express it's needs and intent in abstract cloud-native terms in order to inform a deployment engine. In the case of nitric we take the requirements given by an application and use a deployment engine we've written using Pulumi to deploy it. There is potential here to allow hooking into custom deployment engines and internal platform implementations to help standardise the way application developers integrate with cloud resources while still giving platform engineers the control they need.