Man, I agree but I also really disagree.

I think you should keep complexity down by only using postgres, but just use it as a sequel database until you scale enough that it's a problem.

90% of the time it's never going to scale that far.

When it does, use the tools people have made to do those jobs correctly. Do not hack you way into half-made tools put into a database that isn't specialized in that job.

It seems like you're making your life more simple by having only one system, but you're having that one system to so many things at the same time that it's going to be an absolute kludge in the long term.

Does anyone have experience trying something like this? If you did, is this how it turned out or did it actually work all right?