server1 (app1) -> db1 server1 (app2) -> db2 server1 (app3) -> db3The most important and most used application connects to db1 and is running fine under apache and apache::dbi, but there are some smaller apps that we tried to bundle into this environment that need to connect to other servers running different database instances.
I don't want to eliminate apache::dbi and just use dbi. I don't want to get new machines to handle these smaller apps. I don't think I can have multiple instances of apache on a single Linux server, but am not sure.
I am thinking that I need to set up a standalone Soap Server running on another port to handle the connections to the other databases, without any sort of persistence, which for performance reasons would probably be okay.
Any experience on this matter, or any other design ideas? Thanks.
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.