Interesting test, but I find some of these benchmarks kind of miss the point. Even Grafana's.
The appeal of Thanos/Cortex/Mimir is the long term object storage. The value isn't that it is simpler or cheaper to run. The value is that I can compare data to months if not years ago. It can cost much more than the price of the instances to store good metrics over time even when the data is rolled up.
Scaling the read/write path separately has a lot of benefits as well too, but I would guess that doesn't come up often for most folks.
How much telemetry you can get in/out of your system over a day is important, but how much you can get in/out of it over years is overlooked.
I wouldn't go so far as to say there wasn't much purpose for the ground troops in the context of the goal of eliminating Iraqi military capabilities. It involved some of the largest tank battles in US history such as the Battle of Norfolk and the Battle of the 73 Easting. While we look back at some of these as a steam roll in hindsight, the truth is the engagements were larger than most of the armor battles in WW2 involving the US.
The marine advancement in to Kuwait that was part of a larger multi-national push that much of the Iraqi forces were running from. The push by 1st Inf Div, 2nd ACR, and others on the west was to cut off that retreat.
Combat theaters are large and it is never a good idea to take a narrow view of them and generalize it to the whole. The father of my childhood friend used to tell us how his deployment in Vietnam as an MP was some of the best time in his life. He spent his entire time on a post relatively far from the fighting largely killing his time trying to surf and eat BBQ.
Casualties in warfare is typically used to measure the lose of the fighting force. Not only does it include killed and wounded, it typically also includes troops lost to disease and starvation.
It is pretty common for people to misinterpret casualties as deaths. Especially when people who are not familiar with the terms try to repeat the information to others.
There is also the common practice of not including discounts in revenue. There is a reason companies talk about revenue instead of net sales or net income.
I've never seen AWS give discounts comparable to what Azure provided. Especially to larger companies they want the brand recognition from.
Hundreds of developers were moved from Azure teams to the GitHub org about a year or so ago. Several new features they have added are effectively rebranding/built on top of other Azure projects.
If you think the game was a disappointment, doesn't that imply you already gave them the money? It is not a service. If you bought it 5 years ago, you don't have to pay more to play it.
The appeal of Thanos/Cortex/Mimir is the long term object storage. The value isn't that it is simpler or cheaper to run. The value is that I can compare data to months if not years ago. It can cost much more than the price of the instances to store good metrics over time even when the data is rolled up.
Scaling the read/write path separately has a lot of benefits as well too, but I would guess that doesn't come up often for most folks.
How much telemetry you can get in/out of your system over a day is important, but how much you can get in/out of it over years is overlooked.