Consider the following setup of a postgres cluster:
- Main (write) node - setup to run all in memory using a ramdisk and seting up all tables and such in memory/disabling log writes and generaly free the db to write as fast as possible. I am well aware of the riskiness of that, but also believe/hope it will aquire speed up.
- A second (slave) replication node is set on another instance and writes the updates as soon as it gets them (hopefully, that can be cached so not to slow down the main drive?)
- If a single slave replication node cannot write all updates fast enough, use more instances while hardcoding separate tables for separate machines (as needed).
Can this kind of setup work fast and reliably?
Consider: 10 minutes of data loss once a month is acceptable.