ok I have sent PMs with the details but have not received any feedback, so i will post here in the hope that someone is willing to give some feedback:
Distributed Virtual Dedicated Server Network
The purpose of this document is to give an insight into the possibilities of using a DVDSN. The main aspects of a DVDSN are:
? Content distribution based on location or category
? Use of completely independent IP networks
? Network of independent DNS servers
? Availability
? Centralized management of content and statistics
? Geo Targeting
? Cost reduction compared to traditional dedicated hosting
? Backups through a RAIS (Random Array of Inexpensive Servers)
? Automatic pinging of new articles on the network
? Automatic intra-site linking
? Social Bookmarking
The use of DVDSN is completely transparent to the users as the optimal content distribution is handled by the software and as new servers are added to the network they automatically become available from the management console.
Content can be distributed according to criteria that the webmaster sets, the options are:
1. Category
2. Geographic location
3. Domain name
Availability is achieved by using multiple DNS servers and each server will have different IP addresses for the same host, so say NS1.xyz.com is responsible dns queries for host
www.xyz.com ns1.xyz.com would have an ip address of 123.123.123.123 for
www.xyz.com and ns2.xyz.com would have an ip address of 222.222.222.222 for
www.xyz.com the reasoning behind this is that should that particular network server be down then automatically a secondary dns server would respond with an alternate host ip address.
The communication between the servers on DVDSN is all done through the SSH protocol and therefore all data is encrypted at all times. Replication on the network is scheduled to be performed at regular intervals.
The cost of being part of the network is relatively less expensive that traditional dedicated server packages but offers significant advantages from an availability and SEO point of view.
As data is replicated on the RAIS network, availability and backups are more secure as this is done on geographically different networks.
As data is published the CMS system also automatically notifies the major blog search engines (pinging). Further automations like directory submissions can also be done if needed.
There is also the possibility of having sites on the network automatically link to each other based on criteria set by the webmaster.
The distributed servers may also be used as a gateway for social bookmarking; the biggest obstacle with automating this process is the use of captcha fields. This can easily be solved in the following manner, let?s suppose we have a site where a large mass of users register; what we do is have them fill out a registration form and we use the captcha field from a remote social bookmarking site as follows:
Once a new user registers on one of our network sites a script on a random DVDSN server initiates a session on one of the social bookmarking sites and stores the captcha image and re-displays it to our user that is registering once the user inputs the captcha value we send this value back to the script and if the value is correct we have successfully added a new bookmark, if not the user is prompted again with a new captcha image. Obviously this process will use different user IDs that are constantly created from the different IP addresses on the various social network sites. This process can be maximized if we would use the captcha field also in the login or action (forum posts, blog comments etc) process.
