3 ms·
You can go a long way with read-only replication, as long as you have a good failover strategy for writes before you need sharding... The only time you really n
by tracker1 11y ago
You can go a long way with read-only replication, as long as you have a good failover strategy for writes before you need sharding... The only time you really need sharding is once either your reads or writes require more than a single system in you cluster could keep up with in terms of requests.
That said, using something like RethinkDB (not sql) from the start isn't a bad thing... And depending on your needs Cassandra, ElasticSearch and others are viable options... beyond that there's no need to stick with a single database for different types of data. It should be a case by case basis.
As to the comments about Postgres replciation/failover, it's a pretty sad state imho for an otherwise very respectible database.