Monarch: Google’s Planet-Scale In-Memory Time Series Database
1–10 of 133 posts
Re: Monarch: Google’s Planet-Scale In-Memory Time Series Database
#2Re: Monarch: Google’s Planet-Scale In-Memory Time Series Database
#3Re: Monarch: Google’s Planet-Scale In-Memory Time Series Database
#4Re: Monarch: Google’s Planet-Scale In-Memory Time Series Database
#5I guess its nice to publish at least the conceptual design so that others can implement it in “rest of the world” case. Working with OSS can be painful, slow and time consuming so this seems like a reasonable middle ground (although selfishly I do wish all of this was source available).
Re: Monarch: Google’s Planet-Scale In-Memory Time Series Database
#6I broke this once several years ago. I even use the incident number in my random usernames to see if a Googler recognizes it.
Re: Monarch: Google’s Planet-Scale In-Memory Time Series Database
#7too small for me, i was looking more for the scale of the universe.
Re: Monarch: Google’s Planet-Scale In-Memory Time Series Database
#8I don’t really grasp why this is a useful spot in the trade off space from a quick skim. Seems risky.
Why it exists is laid out quite plainly.
The pain of it is we’re all jumping on Prometheus (borgmon) without considering why Monarch exists. Monarch doesn’t have a good corollary outside of google.
Maybe some weird mix of timescale DB backed by cockroachdb with a Prometheus push gateway.
Re: Monarch: Google’s Planet-Scale In-Memory Time Series Database
#9Re: Monarch: Google’s Planet-Scale In-Memory Time Series Database
#10Interesting that Google replaced a pull based metric system similar to Prometheus with a push based system... I thought one of the selling points of Prometheus and the pull based dance was how scalable it was?