Designing system topology (Physical Architecture)

Steps in coming up physical architecture.

  1. Identify key subsystems of the solution.
  2. Segregate the subsystems physically depending on the resource requirements.
  3. Using baseline size the hardware per node.
  4. Decide on the # of nodes (Factor in scale & HA).
  5. 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
  • Location of users.
  • High Availability – Fault tolerance design.
Number of server nodes
  • Load profile.
  • Growth of load.
  • High Availability – Fault tolerance design.
Size of individual nodes
  • Performance requirement.
  • Capacity of the node.
  • Caching factor.
  • Read operations Vs Write operations.
Environment configs (setup)
  • Security factors.
  • Integration requirements.
Caching factors
  • Performance requirements.
Clustering / replication
  • Latency to sync between nodes.

 

Leave a Reply

Your email address will not be published. Required fields are marked *