Steps in coming up physical architecture.
- Identify key subsystems of the solution.
- Segregate the subsystems physically depending on the resource requirements.
- Using baseline size the hardware per node.
- Decide on the # of nodes (Factor in scale & HA).
- Decide how these nodes talk to each other (Topology)
System load profile
- Users
- Other system (example – data import)
Topology is dictated mostly by
- Solution subsystems.
- Load profile (Scale).
- Fault tolerance (HA).
- Data flow.
- Latency requirements.
What to be sized?
- Network bandwidth & latency.
- Memory requirement
- Disk requirement
- CPU requirement
Location of server nodes |
|
Number of server nodes |
|
Size of individual nodes |
|
Environment configs (setup) |
|
Caching factors |
|
Clustering / replication |
|