Coding guidelines for an IS clustered environment


We would be moving to a clustered environment from a standalone mode. I would greatly appreciate if some pointers/guidelines are available as to what coding practices to be followed. Or rather what pitfalls need to be avoided so that when we move to the clustered environment, the existing code would not break.

One example, is if the flow services are reading/writing to local directories, it will break when we move to a clustered env, if those directories are not present on say the other IS node.

I am looking for a comprehensive list or a checklist of such things to be taken care/reviewed in the exisitng code to ensure that it does not break when moved to clustered environment.

Thanks in advance,