News for hackers. Stuff that matters.
Re:Introducing Private Networking by Ellipsis753 on Tuesday September 10, 2013 @10:53AM (#6360346)
Out of interest what do people use this for?
Re:Introducing Private Networking by zedpm on Tuesday September 10, 2013 @11:08AM (#6360441)
When people have multiple servers, often they need/want those servers to communicate. For example, I might have a web server and a separate database server. So anything on my web server that needs to make a database query would have to communicate over the network to the database server. Prior to this change, Digital Ocean users would have to do that communication over the public internet interface (public IPs), and the traffic would count towards their quota. Now, the servers can have private-side interfaces that aren't internet-facing, allowing this internal communication to take place on the internal network, avoiding the public interfaces and not counting towards the traffic quotas.
Re:Introducing Private Networking by _lex on Tuesday September 10, 2013 @11:29AM (#6360594)
I'd also expect internal communication to be much faster than going over the internet.
Re:Introducing Private Networking by silasb on Tuesday September 10, 2013 @11:48AM (#6360730)
Apparently this isn't the case:

| The latency is actually the same whether you traverse the public or private network because either way it won't get routed out to the edge and back.

Re:Introducing Private Networking by beachstartup on Tuesday September 10, 2013 @12:13PM (#6360978)
the latency will be similar in un-congested conditions (it will stay inside the network edge) but private networks allow the switched network to broadcast less, allowing it to handle "more" traffic across switch backplanes and area networks.
Re:Introducing Private Networking by zedpm on Tuesday September 10, 2013 @12:10PM (#6360945)
Well, the nature of routing is such that, for communication between two VPS in a given datacenter, the traffic wouldn't really "go over the internet", but it ought to still help to have the internal traffic separated from the public side.
Re:Introducing Private Networking by thejosh on Tuesday September 10, 2013 @11:53AM (#6360782)
Say if you have 3-4 cache servers that need to talk to one another, rather than having to give it a public IP (even though it's not routed outside of DO), you can give it an internal IP so all traffic is routed through that network interface instead of the public one - slightly better for security though not perfect as everyone with a DO box can see your private network ip, so you still need to secure it.......
Re:Introducing Private Networking by stefantalpalaru on Tuesday September 10, 2013 @11:54AM (#6360798)
High availability setups. While the heartbeat inter-node communication is low bandwidth, it's unfeasible to run DRBD over a public interface.
Re:Introducing Private Networking by derengel on Tuesday September 10, 2013 @10:56AM (#6360372)
hmm... are we still in hacker news?
Re:Introducing Private Networking by shiftpgdn on Tuesday September 10, 2013 @11:13AM (#6360483)
Not everyone is born with intrinsic knowledge of systems administration. Deriding someone for attempting to expand their knowledge is disgusting and needs to stop.
Re:Introducing Private Networking by positr0n on Tuesday September 10, 2013 @11:11AM (#6360468)
You can be a hacker and still know nothing about how modern website backends are designed.
Re:Introducing Private Networking by xutopia on Tuesday September 10, 2013 @11:47AM (#6360721)
There are lots of people who hack electronics or do desktop programming who have no idea how servers work even though they might be interested. We can't know everything and reminding people of their ignorance when they're asking to know more is discouraging. Stop it.