title: What is the best way to represent routing (one place to next place to next place and so on) in c#
body: <p>I have created a solution which has a routing that provides information from one site (place) to another site and so on , the solution also provides various information which is not directly linked to the site but to the path (one to another) like shuttle days and shipping method by logistics provider.
  Right now I have an entity which has properties like SourceSite , TargetSite , ShuttleDays, Shipping method etc. To know complete route I am using List of this entity.</p>
  
  <p>We have created hundreds of thousands routes using it.</p>
  
  <p>Somehow I don't feel this is the best way to represent the data, because these entities needs to be in order where first's TargetSite should always be next's SourceSite.</p>
  
  <p>Any thoughts to design better.</p>