Component Load-Balanced Component Design

When designing a component that can support load balancing, it is essential that you avoid any sort of location dependency because the component never knows ahead of time which machine it will be running on. For example, you can't depend on the location of specific files, such as C:\mydirectory\somefile, unless you are positive that every server machine has the same file in the same location.

Location dependencies can be subtle. If an object on server A enters a foreign exchange deal into a database at 0900 hours and an object on server B enters a local dealer at 0901 hours, which entry actually happens first? It depends on the time zones the two servers are using. If the servers are or might someday be ...

Get COM+ Unleashed now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.