[moribvndvs]

Also where is this idea that it takes days to ship Python in CDK coming from?

Edit: great, getting downvoted for daring to ask the author to explain a claim. I’m noticing other people asking questions getting downvoted, too. Brigading isn’t a good look.

[sebst]

Stelvio's main selling point here is that you can use our higher-level components for different services and have them automatically configured.

So, you don't have to configure IAM roles, or Env vars manually, as this is handled for you through a concept called linking. https://stelvio.dev/concepts/linking/

In our experience, that alone adds a lot of productivity gains for teams.

[turtlebits]

Why not use CDK L3 constructs (patterns) or the corresponding for Pulumi, since that's what you generate?

[raw_anon_1111]

Higher level CDK constructs do the same thing. But honestly, IAC is one of the easiest thing for LLMs to do and there is plenty of documentation to troubleshoot. There is no reason to introduce this into a company instead of using the official CDK.

[michal-stlv]

Just to make it explicit, I (author) did not downvoted you.

Both me and sebst (co-author) tried to answer everybody and did so politely.

We respect other opinions and Stelvio (as any other thing) might and is not for everybody.

Regarding your question. Well, it depends on the size of the project. Small enough you can do anything fast. I'm working on bigger mostly serverless system on AWS and it did take lot of time to to setup everything with CDK, certainly days.

I believe it would be faster with stelvio as it offers higher level abstractions than CDK - Stelvio was born out of my frustraction with CDK, I was doing lot of things again and again, waiting long for deployments etc.

If someone is happy with CDK, then they should use CDK, it's good too, even for me much better than CF or Terraform.

But if you feel things could be even less cumbersome, with less code and faster, maybe you could give Stelvio a try.

We're not claiming we'll do everything for everybody, we have our opinions and Stelvio is opinionated - shamefully focusing on (app) developers rather than on infrastracture focused people. https://stelvio.dev/blog/why-i-am-building-stelvio/

Thank you for your comment and wish you a good day.

Michal

[moribvndvs]

Thanks for the response. So Stelvo’s sell is through its opinionated approach regarding architecture and defaults. I realize elevator pitches are tough especially when there are lots of competing solutions, but maybe some sort of short and sweet “us vs them” comparison on the home page would make that sell easier. Like many of my peers I’m sure, I’ll admit I have little time and patience to click through to get to the obligatory question of “why us”.

Anyways, not sure who went on the downvote spree or why (it wasn’t one account), and I admit it didn’t seem likely your team would be doing it since you folks were actively discussing, but I couldn’t think of why someone else would do it either. Anyways, sorry and thanks for your time.