State of Affairs
● 3.x has been out for about 1.5 years
● about 70% of users on 3.x
● new UI is helping especially new users
3.x Lifetime
● UI issues are resolved
● completed SNMPv3 support (incl. Traps)
● more pages transitioned
其实3.X的版本一直在改进中。就像之前的版本中，有这样或哪样的BUG一样。不过，3.2.1还算OK。
3.x Problems
● increased number of async. requests
● big number of components and devices
● lots of events
问题嘛 ，不多说了，用过的都懂得。
3.X的架构，不对，是以往的我们再熟悉不过的架构，也许是到了该说Bye的时候了。
Core 4: High Level Goals
● solve current problems
● prepare platform for the future
● improve reliability and scale
● provide further plugin points
Core 4的方向。
RRDCached
● lowered IO load
● improved collection capabilities per
collector
RRDCached的引入。提高RRD的IO读取效率。这个嘛， 比较有用。
Common Collector Framework
● common functionality has been abstracted
● improved consitency across all collection
这个嘛，还没有看懂，也许Zenhub一统数据的时代，也将过去。
RelStorage and memcached
● CMDB/Zope data is no longer stored in flat file but
MySQL instead
● MySQL 5.5.15+ required to take advantage of new
InnoDB plugin
● memcached for intermediary/shared cache for all
clients of CMDB/Zope data
这个嘛，狠！再也不骨ZODB了，对象管理将将由5.5的MYSQL来完成。想不通，这与其它开源工具在管理结构上，还有什么差别。不过也有好一面，至少不再为蛋痛的ZODB的读写再费脑筋了。
PS：为什么不尝试NoSQL？！
Re-written Event System
● RabbitMQ as event system backbone
● multi-stage/process event pipeline
● Lucene index backed event store
● multi-threaded Java based event service with REST api
真的对MYSQL很有信心吗？！
这下看明白了吧，呵呵。新的架构，童鞋们，继续学习吧~
Core 4 Timelines
● code available for build in January
● alphas available at roughly the same time
● release end of February
● move to Github and JIRA April/March
最后，时间表，其实4真的离我们不远了。
个人还是比较期待的~哈~
