4 ms·
why not just create a vpn between the nodes with another private IP space and send your data through that?
by 0x006A 12y ago
why not just create a vpn between the nodes with another private IP space and send your data through that?
- cbhl 12y agoPerhaps that would become a bottleneck at Instagram's scale?
- blackaspen 12y agoI believe it becomes a bottleneck at the scale of like, 5 servers. This is a tough problem, Neti is a heck of a lot better than tons of VPN connections everywhere.
- justizin 12y agoyou could probably do hundreds of servers, but you would want to die.
- toomuchtodo 12y ago"This task looked incredibly daunting on the face of it; we were running many thousands of instances in EC2, with new ones spinning up every day. In order to minimize downtime and operational complexity, it was essential that instances running in both EC2 and VPC seemed as if they were part of the same network. AWS does not provide a way of sharing security groups nor bridging private EC2 and VPC networks. The only way to communicate between the two private networks is to use the public address space." That is essentially what Neti does, except instead of static mappings, its dynamic and software configurable (which is pretty much the only way to go when you're entire environment is virtual and the underlying network equipment is out of your control).
- 0x006A 12y agoUsing a VPN would still be an option. Why write essentially your own VPN (neti) instead of using an existing VPN solution? VPC is not the only VPN you can use on EC2.
- toomuchtodo 12y agoI believe Neti was a better solution at their scale (thousands of VMs, a dynamic production environment, etc).
- Rapzid 12y agoSo I guess it was a bit of hyperbole. A straight forward solution to a straight forward problem.
- deleted 12y ago[deleted]