Stacktape

Stacktape CEO sharing my honest take on DevOps. Today, we're launching the next iteration of Stacktape. It's a huge upgrade for DX (developer experience) for our users. Our approach has always been IaC (Infrastructure as a Code) first. Yes, it's a bit less convenient to deploy your first app this way. But it's also a much better approach in the long run. We also understand that IaC is less convenient than using GUI. But it doesn't have to be so. Stacktape Interactive Config Editor allows you to configure infrastructure for virtually any use-case with just a few clicks. In minutes. Yes, Stacktape is limited to what AWS has to offer. But it also supports all of the most commonly used infrastructure resources AWS has to offer. In a way, that makes it a breeze to use them. Unlike other DevOps platforms (or "developer platforms"), we're AWS only - allowing us to leverage all of the AWS "goodies" in the most convenient way. We don't simply spin up AWS EKS (Kubernetes) clusters and deploy everything to them. We allow you to choose the best compute platform for any given use-case - be it Lambda function, Fargate container or EC2 container. You might ask, "why don't you use Kubernetes" - the gold standard atm. And the answer is simple - we don't have to - AWS ECS is totally sufficient for most of the use-cases. And it's also free (no need to pay for the EKS control plane). To summarise. If you're only using AWS for your infra, Stacktape will be the most convenient, reliable and cost-efficient deployment platform. If you also need to use other platforms, then it's not for you. Let me know what you think. Especially if you disagree with my opinions.

Love this! Does stacktape also help with choosing between AWS lambda or AWS EC2 and other AWS resources for different use cases?

Whoa, this is cool! Finally, a way to use AWS without needing a PhD in DevOps. Gonna give this a spin for my next project – see ya later, server headaches!