从MCOD/Central Instance开始乱弹

企业的系统架构正在变迁。以前是一个个单独的小系统，之后当业务变得复杂的时候，企业引入了越来越多的解决方案，为了避免解决方案之间成为信息孤岛，各种作为proxy和集成器的中间件应运而生，系统似乎不是分布式的，都不好意思跟人打招呼。而当企业的信息系统变得更加复杂的时候，似乎应该回归到一个中央访问点的时候了。

从SAP对DB的MCOD（Multiple Components in One Database）的DB layout的支持，到近期三星电子的全球性single instance实施的上线——从此三星将运行世界上最大的单一实例的ERP系统。

也许，底层软件和硬件的支持应该继续分布式，继续云下去，可是构架在此之上的业务软件，应该越不分布越好。否则，系统的维护将慢慢变得不可能。

---------

MCOD at a Glance

Kehinde Eseyin (Systems Support Manager) posted 4/27/2009 | Comments (1)

Definition
MCOD is an acronym for Multiple Components in One Database.
With MCOD, SAP Netweaver components are installed and managed in a single database. Individual system data is isolated in the database. Every system application runs as if they were installed separately

Features and Benefits
Single logical and physical database instance
Reduction in the number of databases to administer
Optimizing of licensing for database and database management tools
Flexibility in change management and maintenance as result of componentization of systems
Ease of database and system maintenance (patching) because all system uses the same release of database.
Individual systems can be upgraded independently of the other system
Independent tuning and administration of systems
Synchronized backup and restore strategy for all MCOD systems is possible.

Administrative Challenges and considerations

Duplication of maintenance and support effort for multiple applications
Single point of failure
High availability solution cost
High system resources and consumption need