3 ms·

This only makes sense if you're in a world where you're switching backends more than once, which means you're not seriously programming, you're just burning VC

• jrockway 3y ago
  I agree with this. For internal apps, pick a system and stick with it. If you're excited by Datadog's marketing pitch, just buy it and use it. It will not make or break your startup; like if your Datadog bill is what's standing between you and profitability, then you probably didn't actually find product/market fit. Switching to Prometheus at that point also won't help you find product/market fit. In the 2 jobs where I've set up the production environment, I just picked Prometheus/Jaeger/cloud provider log storage/Grafana on day 1 and have never been disappointed. You explode the helm chart into your cluster over the course of 30 minutes, and then move on to making something great (or spending a week debugging Webpack; can't help you with that one).
  • esafak 3y ago
    You had better have PMF if you pick Datadog! https://thenewstack.io/datadogs-65m-bill-and-why-developers-should-care/ https://thenewstack.io/datadogs-65m-bill-and-why-developers-...
• nijave 3y ago
  Also useful for local dev (you can still use it locally without a SaaS backend) and it helps with interoperability. Infrastructure like Envoy and nginx can emit spans that integrate with 1st party code and other 3rd party code. OSS libraries are more likely to implement an open standard so they just plug and play and emit data for internal things they're doing (especially helpful for things like DB and HTTP)