3 ms·
There’s a fair amount of “duplicated” costs. For example, if you’ve got a large observability push internally you’re not shutting down the existing system and a
by rgrmrts 4y ago
There’s a fair amount of “duplicated” costs. For example, if you’ve got a large observability push internally you’re not shutting down the existing system and are likely experimenting with multiple routes. Instrumentation etc takes time so a company might be running multiple services. Eventually the infra teams will decide what to commit to but before everything migrates over there’s a period where developers need to be migrated over (and this can’t be too sudden or you lose productivity).
I think a lot of infra costs are inflated when the company is scaling. I don’t think this is “bad infra teams”, it’s just the cost of smooth transitions to better tech. This has been my experience anyway, on both the implementor side and consumer side.