Oracle Coherence 3.5 读书笔记之1 - 前言

准备系统的学习一下Oracle Coherence，找了一下，只有一本书： Oracle Coherence 3.5
Coherence目前最新的版本为12.c, 虽然版本老点，但核心的东西应该是一样的，而且评价也不错。接下来的几周，集中精力先把这本书看完。

Coherence原属于Tangosol, Tangosol于2007年被Oracle收购，Coherence从此归入Oracle的中间件产品。

先看一下前言，引用了两句谚语：

Once you open a can of worms, the only way to re-can them is to use a bigger can.

If builders built buildings the way that programmers wrote programs, the first woodpecker to come along would destroy civilization.

都是用来揶揄编程人员的，不过当今编程人员面对的最大挑战就是复杂性，硬件越来越复杂，OS越来越复杂，编程语言和API越来越复杂，我们构建的应用也越来越复杂。

文中提到了一个单词：ilities，其实就是非功能性需求，其中有四个最重要的为：
- Availability，业务连续性
- Reliability，指信息的真实性，可信程度
- Scalability，系统可扩展性
- Performance，性能

Oracle coherence正式被设计以保证上述四个非功能性需求的。

接着，根据重要程度，作者依次给出了三个建议。

1. 
   

2. 架构很重要，特别是对于可扩展的系统

architecture matters, and in systems of scale and systems that require availability, architecture matters absolutely!

Availability, reliability, scalability, and performance must be the core tenets of an architecture, and they must be baked into and throughout that architecture.

• 熟练掌握你的工具

• 眼见为实，测试（边界测试，压力测试）以了解系统的极限。
  

  don’t believe it until you see it; make sure that you push it until it fails. While testing, if you don’t overload the system until it breaks, then you can’t be certain that it will work. If you don’t pull the plug while it’s running, then you can’t be certain that it will handle failure when it truly matters. Don’t be satisfied until you understand the limits of your systems, and until you appreciate and understand what lies beyond those boundaries.

• 
  在作者介绍部分，推荐了两个coherence相关的博客：
  1. http://blackbeanbag.net/wp/
  2. http://coherence.seovic.com/