3 ms·

Interesting. Where do you put postgres in this landscape?

• Joeri 13y ago
  My opinion is that if you're going the rdbms route, you should keep everything on a single instance (mirrored to a hot backup ofcourse). As soon as you start managing a menagerie of servers with intricate programming logic to shuffle data back and forth, the nosql solutions will be a better fit. So, for any rdbms i would advise using it where it can handle the load on one instance, or possibly a few with a very simplistic sharding model (e.g. we never shard the schema, but we do host different customers on different oracle instances, without any data shared across customers). I haven't worked enough with postgres to know what loads it can handle, but i'm sure there are plenty of cases where a single instance is just fine.
  • voltagex_ 13y ago
    How do you work out what load Postgres can handle on what hardware? (Same question for anyone here who knows MSSQL)