Hi all, I have 2 servers online and wish them to communicate and exchange information with each other at times. I have been developing a web application which is extremely CPU-intensive, and since I don't want to overload the main server which deals with the apache/php/mysql stuff, I got a separate server (a phenom) to deal with it. I prefer the communication to be secure, low latency, scalable and two-way ie. either server can initiate communication with the other. As the number of users increase, I will need to add more quad-core servers. What would be the easiest/quickest-to-implement way to do this? Is there a daemon I could use to do this, or would I need to develop my own? Since I have only ever had a single server, I have never had to do this before, so wouldn't have a clue as to where to start. (I Googled "server communication" but got a pile of semi-useless links) TIA
D Steward wrote:> Hi all, > I have 2 servers online and wish them to communicate and exchange > information with each other at times. > > I have been developing a web application which is extremely > CPU-intensive, and since I don't want to overload the main server which > deals with the apache/php/mysql stuff, I got a separate server (a > phenom) to deal with it. > > I prefer the communication to be secure, low latency, scalable and > two-way ie. either server can initiate communication with the other. As > the number of users increase, I will need to add more quad-core servers. > What would be the easiest/quickest-to-implement way to do this? > > Is there a daemon I could use to do this, or would I need to develop my > own? > > Since I have only ever had a single server, I have never had to do this > before, so wouldn't have a clue as to where to start. > (I Googled "server communication" but got a pile of semi-useless links) >it depends on what you want to exchange. you don't need to design server software. you can use http (if running an http server is ok), stunnel, ssh, ... you can even use mysql!
Check out the OpenAMQ project for a secure, scaleable messaging engine and protocol. It may be overkill for what you want (maybe not), but should look good on the resume. http://www.theserverside.com/news/thread.tss?thread_id=41008 http://www.openamq.org/ On Tue, 18 Mar 2008, D Steward wrote:> I prefer the communication to be secure, low latency, scalable and > two-way ie. either server can initiate communication with the other. As > the number of users increase, I will need to add more quad-core servers. > What would be the easiest/quickest-to-implement way to do this?------------------------------------------------------------------------ Jim Wildman, CISSP, RHCE jim at rossberry.com http://www.rossberry.com "Society in every state is a blessing, but Government, even in its best state, is a necessary evil; in its worst state, an intolerable one." Thomas Paine