How does the multi-node version handle high availability and automatic failover?

Are those included or are they paid add-ons?

Short answer is: The 2.0 release won't natively support automated failover, although you can build around using PG tools like physical replication + Patroni. But these capabilities are certainly things we are working on.

Per the PR notes:

  The current implementation has many more limitations 
  that will be addressed over time:

  - HA and replication has to be managed node-by-node. 
    This will be improved with native replication.

You can utilise multinode data replication for high availability of data, however it is still necessary to use an external tool for HA of the access node, which distributes data and queries to data nodes.

How does the multi-node version work with data compression compared to the single-node version?

I like how on a single-node I can utilize data compression and get a 95% storage saving.

In the current version, you can execute `compress_chunks` on each of the data nodes and enjoy those same savings (and will work transparently with queries, as before).

In subsequent releases, we'll add full support of compression, e.g., just create a compression policy on the access node and you are off and running.

Sounds great. So I just manually execute this `compress_chunks` command once on each data node and then I have compression enabled forever on those nodes?

Not yet, I should have been clearer:

compress_chunk operates on a single chunk, the way to define "compress all chunks older than 1 week is":

   SELECT compress_chunk(i) from show_chunks('conditions', older_than => INTERVAL '1 week'); 

https://docs.timescale.com/latest/using-timescaledb/compress...

So you'd need to setup a cron job that runs that script every night or something...at least until we release compression policy support.

Does this product "exist" yet or is it vaporware we're putting our email addresses in for? Page seems very light on info or even pricing.

The product exists indeed and it’s very stable. Been out there for years.

Froost or Notion? Froost's homepage says "subscribe for early access".

Yeah. I googled Froost out of curiosity and I was spot on, the project barely has anything but a landing page and a post on Indie Hackers about said landing page launching a few days ago.

We actually have a sidenote that mentions that GA can be used for event-based tracking, but we've decided to skip over it in v1 of the guide because it's missing some critical analytics functionality. We're focused on the big three event-based analytics tools for now, but are going to add more info on tools that can be used for event-based analytics, but aren't primarily designed for that purpose, e.g. Pendo, GA, etc.

Also, there's no mention at all of GA App+Web (launched August 2019) - which is clearly the future of Google Analytics and uses an event-based model.

Thanks for bringing this up. Just to clarify, the base version of GA provides an event-based model. GA App+Web is a feature of GA that's aimed at sharing/consolidating info between websites and mobile devices. We're focused on the web side of things, as we've insofar only written a web analytics article. We suspect GA becomes a bigger player when we take a look at mobile analytics, but we haven't fully delved into that yet.

I love the super clean design of your main website. Is that based off a template or made from scratch using UI library?

Yea it's really nice. I looked through the Github repo could couldn't figure out what library they used.

Would love to know what css/ui they are using.

Thanks :) We started off with a theme which is using Bootstrap and the illustrations are created by mixing humaaans.com characters with undraw.co illustrations. The font we used is paid font, so we couldn't make the repo open. Tech stack is React with Gatsby hosted on Netlify.