Show HN: Stacktape – Full power of AWS with Heroku-like experience
What about observability? Logging, monitoring, alerting? Security infrastructure, everything from setting up IAM with better security for both human and machine users, to vulnerability scanning, WAF, anti-DDoS, TLS certificates, DNS, edge caching&#x2F;CDN...? Backups? Separate environments for development, staging, production, that stay consistent?<p>Look, your landing page example is cute, but it&#x27;s not fully production ready. And by the time you finish adding everything to make it fully production ready, you&#x27;ll be back up to the 600 lines of configuration that you&#x27;re currently demonizing.<p>Look, this shit is hard. I get it. I recently got mindfucked by the intricacies of single table design in DynamoDB, and the sheer complexity of doing that correctly, for the sole benefit of hiring fewer $200k&#x2F;year engineers, plus the headache of trying to hire the right ones, plus their post-hire management overhead. And that&#x27;s barely DevOps adjacent!<p>I&#x27;m not convinced that you can truly remove the complexity. The more features you throw on your PaaS, the more configuration options you expose. Eventually, the configuration for your PaaS gets complicated enough that you hire an engineer who knows the PaaS very well and they become your DevOps engineer. Then you realize that you didn&#x27;t actually solve your problem, you just made it harder, because the PaaS never exposes everything you actually need, so either you need to wait for the PaaS to implement it, or you start to migrate off it.