Within your solution, you have components such as Alfresco Share, Alfresco Content Services, database, index (Solr), transformations, and the content store. As illustrated in the following diagram, some of these components can be clustered while others are optional.
- Alfresco Share
- Alfresco Content Services
- Content store
- Database
- Transformation Server
- Solr 6 index
It is important to decide how many installations you need and which of the specified components you will put on which node.
To explain this further, let's consider an example. Assume that your application has six nodes. Ideally, it's recommended that you should have one component on each node. So, for example, node1 has database, node2 is content store, node3 is Alfresco Content Services, node4 is Alfresco Share, node5 is Solr, and node6 is Transformation Server.
Use the following table as a template to design your solution.
| Clusters/ nodes | Alfresco components | DNS | IP address (optional) | Additional information |
|---|---|---|---|---|
| 1 | Database | |||
| 2 | Content store | |||
| 3 | Alfresco Content Services | |||
| 4 | Alfresco Share | |||
| 5 | Solr 6 | |||
| 6 | Transformation Server |
However, you can configure your distribution differently. Each distribution and clustering solution has its own advantages and disadvantages. To configure distribution and clustering optimally, contact Alfresco Consulting or your Alfresco certified partner.
For a better understanding of initiating clustering for high availability and high throughput, see Scenario: Clustering for redundancy and Scenario: Clustering for high throughput.