Explore >> Select a destination
|
You are here 
|
blog.oodle.ai | ||
| | | | |
blog.bitdrift.io
|
|
| | | | | Recently the observability world has been abuzz with discussion of "observability 1.0" vs. "observability 2.0," and how this transition impacts platform and application teams looking to get the best ROI on their observability investments. While a lot of this discussion is, not surprisingly, marketing fluff, there are some real technical nuggets inside that are worth calling out. In this post I am going to explain my perspective on observability 1.0 vs. 2.0, explain how bitdrift Capture fits into this story, and finally argue that Capture deserves its own version bump to observability 3.0 given the step function in capability and ROI it offers over 2.0. Let's dive in! | |
| | | | |
tech.trivago.com
|
|
| | | | | Scalability and availability are key aspects of cloud native computing. If your microservice takes five minutes to start up, it becomes very difficult to meet the expectations because adjustment... | |
| | | | |
last9.io
|
|
| | | | | A deep dive comparison between Thanos and VictoriaMetrics: Performance and Differences | |
| | | | |
lakefs.io
|
|
| | | An update on all the latest tools and trends in the data engineering space for 2022. | ||
