Ok, djago+whathever db just works. Postresql is behind db,(ok, I'm a fan!!) there are features that django simply cannot manage. Seeking for performances in postresql I'd use triggered partitioning, triggered retention policies and fine indexing with index space on dedicated ssd ... Well dba stuffs :) About consistency, streaming replica, django that exploit switch on r/wand switchover failure. About 'in memory tables' PG has, as many others, prepared transactions, I've found great benefits with tables over 1Tb (Pg 9.3, not partitioned) ...can Redis do that..? Gess it need Tbs of Ram.. Cheers.
Comment
Ok, djago+whathever db just works.
Postresql is behind db,(ok, I'm a fan!!) there are features that django simply cannot manage.
Seeking for performances in postresql I'd use triggered partitioning, triggered retention policies and fine indexing with index space on dedicated ssd ... Well dba stuffs :)
About consistency, streaming replica, django that exploit switch on r/wand switchover failure.
About 'in memory tables' PG has, as many others, prepared transactions, I've found great benefits with tables over 1Tb (Pg 9.3, not partitioned)
...can Redis do that..? Gess it need Tbs of Ram..
Cheers.