rk2

The idea here is to get your modules more organized, so you can avoid actually copy pasting, but rather using version controlled modules.

Thats nice :) Hopefully someone with less or more experience will.

It's open source, why not give it a try to overcome the skepticism.

To clarify, it doesn't magically generate Terraform, it uses concrete Terraform modules that you define and maintain and maps them to resource declarations that are made in the application code using CDKTF.

btw - the IfC section starts at 14:39 in the video

Imagine the potential of Infrastructure from Code (IfC) alongside IaC - it could change how we handle infra deployments in the future.

In addition to efficiency in deployment, IfC can also help ensure that all deployments are compliant with regulatory requirements, security policies, and internal best practices.

Not quite,

Nitric infers the necessary cloud runtime by building a spec based on the resources you've imported into your application code.

At deployment time Pulumi is used to provision the resources (because we think it is an awesome tool).

Note that we could have also opted for any other IaC like CDKTF, and that you could either modify our providers or implement your own providers using your IaC of choice.

It is worth noting that the Nitric team (whom I work with) aren't suggesting that Nitric is an alternative for every Terraform project out there.

However, there are many use-cases without bespoke infra needs where it does suit.

Our hope is that people who genuinely are looking for assistance with their cloud deployment needs evaluate Nitric against their own projects requirements.

The Nitric providers which handle the provisioning piece are IaC.

Rather than poking around bespoke IaC on a per-project basis, you have the opportunity to inspect modularized and tested IaC which in this case is written in Pulumi and maintained by either the Nitric team or your team if you need to customize and move away from "out-of-box".

I work with the maintaining team, we're happy to discuss more. If you're curious then hop into our discord.

"I started to look at new approaches to infrastructure, searching for automation to solve the challenges we were facing with Infrastructure as Code tools like CDK and Terraform. The latest innovations with Infrastructure from Code were an ideal fit to help our small team move quickly and efficiently."

Thanks for sharing ... his photography is surreal.

Done a couple of shoots for weddings as a side hustle, pretty long days work and far more draining than SW Engineering work ...

I agree with this sentiment, I've switched back and forth for months/years at a time based on what my body required ...

As a result, I don't ever feel guilt anymore about impulsive decisions. When the opportunity arises to experience something new, I'll take it.

The landscape view is cool, nice to be able to drill down into sub-sections ... e.g. https://landscape.cncf.io/serverless

Before you categorise something as 'unncessary complexity' maybe it is worth taking some time to understand whether or not the problem that your company is trying to solve aligns with the goals of idea being presented.

We probably are doomed if there is no push back and debate with the vocal minority. Silence is often mistaken for complicity.

A star is also a good way of bookmarking a repo which you see yourself using in the future.. or just to watch its progress.

Agree and also have to consider that there is a need for solutions for cloud providers other than amazon.