top | item 11367283

(no title)

sspies | 10 years ago

Actually, each tenant has just a view of the full table. There is no need to save the same routes for each customer over and over again. Furthermore, there is aggregation done before a route is installed on the switch.

discuss

order

bogomipz|10 years ago

Can you talk more about how your product works? For instance this reminds me of an Internap product:

http://www.internap.com/network-services/miro-controller/

Their strategy I believe was that if you were optimizing for latency(as opposed to price if you had multiple transit providers), was that it would do traceroutes out to your TOP 100 destination AS and find the AS path with the lowest latency and set the route preference within your AS to prefer a certain transit provider outbound.

How does your product work given that you don't have any control or interaction with the AWS AS?