Content Server Search Architecture and Scaling

Back End Scaling – Admin server

Livelink admin server can be scaled to improve performance and task distribution for high volume requirements.

Search architecture can be broken down into three parts:

• Data Flow – It consists of Extractor, IPool, DCS. It also contains Classification Importer and Prospector Importer
• Search Grid – Update Distributor, Index Engine, Index, Search Engine, Search Federator. This is the scalable part of search architecture.
• Search manager – Search Federator, Search Manager

Search Architecture

Scalability can be achieved by the addition of more Admin server, search federators and Partitions. A diagram showing all three added to the architecture is shown below.

Scaled Search Architecture

Front End Scaling – Web server

Horizontal scaling

In horizontal scaling we have installations done of different physical servers. Thus if one server goes down we can still have others to share the load and keep the application up and running.

Horizontal Scaling

Vertical scaling

In vertical scaling, one physical server has two or more installations done no it. This allows optimal use of server’s resources and also reduces the cost of hardware since we can get two or more installations done at the cost of one.

Vertical Scaling

Ideally, a combination of horizontal and vertical scaling is the best solution.

Horizontal and Vertical scaling