Live data from Hacker News

Monarch: Google’s Planet-Scale In-Memory Time Series Database

micahlerner.com

1–10 of 133 posts

Re: Monarch: Google’s Planet-Scale In-Memory Time Series Database

#5
A lot of Google projects seem to rely on other Google projects. In this case Monarch relies on spanner.

I 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

#8
post #4

I don’t really grasp why this is a useful spot in the trade off space from a quick skim. Seems risky.

There’s a good talk on Monarch https://youtu.be/2mw12B7W7RI

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

#10

Interesting 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?

Prometheus itself has no scalability at all. Without distributed evaluation they have a brick wall.
Post reply on HN