3 ms·
I'm OP, and if I could I'd use Postgres everywhere, I want to know exactly when other stuff is useful and necessary, the trade offs, so I can make judgement cal
by techsin101 6y ago
I'm OP, and if I could I'd use Postgres everywhere, I want to know exactly when other stuff is useful and necessary, the trade offs, so I can make judgement call for myself and team.. That yes we don't need this, regular sql server would do with some pub/sub.
- throwaway_pdp09 6y agoI can't tell you when to use it, I can clearly tell you when not to (as has the other guy here). If 1 machine postgres suffices, stick with it. If it does not, would buying more processors/memory/disk fix that? If so, stick with it. The big data stuff is when you really have too much data to deal with in one box and literally cannot get round that. The tradeoffs are (my limited experience): cost in terms of buying a stack of boxes. Cost in terms of learning a massive new software stack. Cost in terms of "it scales almost infinitely but each node processes so much less". I gave a link before, I hope that showed something useful. Here's another, see article and paper https://html.duckduckgo.com/html?q=scalability%20%22at%20what%20cost%22 https://html.duckduckgo.com/html?q=scalability%20%22at%20wha... Does that provide (at least the beginnings of) an answer?
- throwaway_pdp09 6y ago(that last line could come across as rather snotty; was not intended that way. Meant to imply I'm happy to try to answer any questions to the very limited extent that I can).