B*****g
发帖数: 34098 | 1 【 以下文字转载自 Java 讨论区 】
发信人: goodbug (好虫), 信区: Java
标 题: Re: Job with Oracle PL?
发信站: BBS 未名空间站 (Tue Dec 20 17:01:25 2011, 美东)
It's a bit of everything.
1. Relational DB doesn't scale that well compared to NoSQL due to
transaction
support requirement. More DB nodes will certainly degrade performance. How
bad
is probably dependent on how data can be partitioned. On the other hand,
transaction support is a requirement for most non-trivial websites
nontheless.
2. Oracle license is very expensive, you pay for every CPU added to that.
Once I notice DB a performance issue and I asked DBA to segment the data,
and
I was told we'd need to pay extra $$$ if we did that too. On the other hand,
typical stack on a cluster has little to no license fee. Linux+Tomcat+Spring
+Hibernate stack, for example, is popular and free.
3. Caching, caching is probably single most effective mechanism to improve
throughput. And caching is expensive on DB server due to its centric
approach.
SSD array is very expensive. On the other hand, when caching is done on
application server. You can have distributed approach and it's typically
much cheaper.
vendor
SP |
|
