What are strong arguments against using the same programming language to implement Infra-as-code?
Let’s say I have a cloud native service implemented in Rust. I’m using lambda , API gateway, DynamoDB and S3.
What are strong arguments against using the same programming language to implement Infra-as-code?
Let’s say I have a cloud native service implemented in Rust. I’m using lambda , API gateway, DynamoDB and S3.
@mattiem yeah but in my particular case the entire project is Rust only (plus some bash scripts) and AWS has a pretty good Rust SDK. I’d rather stick to keep using only Rust. On the plus side the infra can leverage more deep integration with the project. I plan to use some macro to autogenerate the entire AWS API gateway config.
On the cons side I had to build basic deploy setup infra logic from scratch but it only took me a day.