Basically, we have internal services that are being accessed from client machines, whether they be true clients, or loaders of information from external sources. In order to increase our ability to handle the throughput from the clients, they are going to farm servers.
These services fall into four categories:
- WCF WF4 services
- DCOM components (that might or might not be enlisted in DTC transactions)
- Appian process endpoints
- ASP/ASP.NET services
From what little I understand, there's no central pooling mechanism- it's sort of peer other than the one specialized switch? As I'm working from the development side, I'm most concerned about troubleshooting (especially in the case it is an intermittent problem which could indicate a problem with one of the nodes) and deployment and testing.
I feel a little better based on the last 5 minutes of the presentation, even though he didn't go into enough detail on that part, which had to do with gracefully removing a server from the pool and direct connection capabilities to a single server. But in all reality, it was very overwhelming, especially as this isn't something that I'm going to be directly involved with on a day-to-day basis to bridge the receiving of the information to practical use.