Seems to be more, how to get bgp packets to an open flow server to do stuff...
I'd be interested as a network techy to see how they actually do the rest of bgp on openflow/sdn, like holding multiple full tables on the server and how the switch has enough memory to deal with that amount of information...
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.
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?
I'd be interested as a network techy to see how they actually do the rest of bgp on openflow/sdn, like holding multiple full tables on the server and how the switch has enough memory to deal with that amount of information...