Experience-with autoconfiguring a network with IP addresses

Author(s):  
A. McAuley ◽  
A. Misra ◽  
L. Wong ◽  
K. Manousakis
Keyword(s):  
2015 ◽  
Vol 22 (2) ◽  
pp. 71-71
Author(s):  
Finn Kuusisto
Keyword(s):  

2016 ◽  
Vol 100 ◽  
pp. 12-27 ◽  
Author(s):  
Ahmad Jakalan ◽  
Jian Gong ◽  
Qi Su ◽  
Xiaoyan Hu ◽  
Abdeldime M.S. Abdelgder

In this paper, we have created a chat application which uses socket programming for communication and all of the messages are saved in mongoDB. We have taken Docker application and hosted it on a three-node swarm cluster. This cluster uses Docker swarm technology to create a private network through which each of the nodes can talk to each other along a specified RPC port. The application runs in each node as a service and all load coming to the application has been balanced across three IP addresses in the swarm. This creates a distributed system and each node can act as a manager or a worker in the system. This technique helps to decrease the execution time to run servers on the cloud and can help improve the feasibility of online servers provided by the IT companies.


Author(s):  
Laura Carrea ◽  
Raul Almeida

The Internet architecture of today does not seem suited to the current Internet usage, as the application layer is more and more content-centric, while the network layer is ossified around the IP concept. In this chapter, the authors explore a redefinition of the whole Internet architecture where nothing is taken for granted, especially IP addresses. The review focuses on the forwarding and topology components of the EU FP7 PSIRP architecture and on a few of the problematic issues and the ongoing discussions around a pioneering clean-slate design of the way to organize networks.


Sign in / Sign up

Export Citation Format

Share Document