D Steward wrote:
On Tue, 2008-03-18 at 10:06 +0100, mouss wrote:
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!
Hi, the amount of data being exchanged is very small (<1k), but it
*must* be low-latency. Communicating via http/mysql would mean both
servers polling for changes to a database or flatfile db/logfile, which
would be highly undesirable.
How often does the data change and how critical is it to have real-time
results. Web sites often have thousands of people getting copies of the
same thing, or at least computed from the same values even if they are
the same only for a short period of time. One approach is to put
memcached between your web application and the database for extremely
fast repeated access to the same data. It is just a cache layer, though,
you still need a persistent database underneath.
http://www.danga.com/memcached/
--
Les Mikesell
lesmikesell@xxxxxxxxx
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
