4 ms·
> Sometimes when browsing documentation for a service or API you will find that the old way is deprecated, but the new way that they recommend you use is still
by jrockway 8y ago
> Sometimes when browsing documentation for a service or API you will find that the old way is deprecated, but the new way that they recommend you use is still in beta or alpha (!).
Familiar.
- ebikelaw 8y agoAlso familiar: monitoring frontend is tragic-comic with no units and inscrutable data. It’s cute that the author thinks the internal version must be a lot better! On the other hand, the article doesn’t mention Stackdriver Profiler, which has an amazing UX. Definitely recommended if you are spending significant money on CPU at GCE.
- dantiberian 8y agoNice, I haven't used the Profiler yet, will check that out soon. What languages have you used it with? I'm looking to use it with the JVM profiler.
- mmclean 8y ago[SD APM PM here] Yep, we support Java / JVM, Node.js, and Go; Python is coming soon
- wikibob 8y agoWhat’s the long term plan here with StackDriver and OpenCensus? Are you eventually going to support high cardinality events with the ability to aggregate and then break down (as opposed to say Prometheus which pre-aggregates, so you can’t break down to debug, and doesn’t support high cardinality).
- wikibob 8y agoWould you be willing to add a contact method in your profile (twitter/email) for some offline questions?
- clhodapp 8y ago"Beta" is kind of an awful purgatory state on GCP. We all know that most of their beta stuff is actually really well-tested and stable (it's even mentioned in this article). They also know it themselves and seem to assume that people will be willing to start using their products when they are in beta. However, they have an ill-advised blanket policy that beta products are not covered by SLAs, which ends up meaning that no responsible decision-maker wants to build anything in production on top of anything tagged "beta". In many ways, you get forced to treat beta in exactly the same way as alpha even though you know that it's actually much more reliable. I strongly believe that Google and its users would be much better off if Google used beta to mean "SLA'd but with documented feature gaps and a shortened deprecation period" and kept stuff that they are not willing to SLA in alpha.
- wikibob 8y agoI totally agree, this is a serious problem. Because even if you understand that they mean “hey it’s Beta but it’s fine for production”, if you choose to use it and it breaks, all blame will point back to you for making an unwise choice. There is a terrific explanation of the difference between Alpha, Beta, and Stable in the Istio project [0]. Istio was started by GCP, so while this isn’t officially Google’s definition I imagine it’s peobably the same. It basically says, Beta is mostly usable in production, but things might change in the future that require work from you to upgrade. [0] https://istio.io/about/feature-stages/ https://istio.io/about/feature-stages/