Absolutely agree, I tried it out for a short personal project and was disappointed with the bad documentation and even worse libraries that I found. I'm assuming large companies have their own internal libraries/ORMs for this, and that's how it is intended to be used.

In terms of the actual technology itself, it's very interestingly built, and as the poster above me mentioned, with a ton of caveats to the promises it makes.

It is one of very few technologies that I need to get a pen and paper and some quiet time to decide on a table schema. Most of the time I need to redo it after coming up with new query requirements.

I hate and love it at the same time.

It’s because it is just really expensive (both in time and money) to do basic things like a table scan.

That's actually one of the caveats that comes with unlimited scalability: You must design your application to not require full table scans.