zlacker

> Just adding another service is easy, but making them work seamlessly together is much harder.

This argument in favor of PaaS makes a lot of sense to me. A PaaS vendor might say, "sure, you could set up your own observability layer, configure storage for it, troubleshoot that one service that can't connect to the API's endpoint, etc. Or you could just check the "observability" box on our dashboard and boom, there it is."

I'm currently at a company that really likes setting everything up from scratch. And the amount of time my team has spent building out a platform, as opposed to providing business value, is really sobering.

>>Taikon+(OP)
Yeah that same experience at our previous startup was one of the main reasons why we started Modelence. We got to a point where we had a dedicated 3-4 cloud platform engineers (out of the 20 engineers total) working full time only on things like observability, alerts, performance, cloud deployments, etc, none of which was specific to our product.

And when you take a step back and think for a moment, it just doesn't make sense that you have to run a whole separate team for something that's pretty much reusable across products.