| soulis 2006-06-25, 7:23 pm |
| I am posting this to general because I am requesting justification as to get
some feedback on the scalability and efficiency of each solution.
Scenario:
A biztalk application will receive different types of xml files, and flat
files. Its goal is to transform the files received, mostly the flat
structures with an interchange likely, and batch-submit them to an ftp box,
using pre-aggreed upon schemas.
It is required that if a previous ftp deposit is claimed that it hasnt been
received, another deposit to be made (a window for that type of action can be
small - 24hrs to a week max).
Based on your experience, should the application temporarily store the
contents from different files in a database construct? or should it use
filesystem folders and naming conventions, with probably a small set of
metadata saved in a db to achieve the same functionality?
Any responses, input would be appreciated; again I want to hear about
efficiency and scalability of using the sql adapter vs file system for
processing a diverse file set (again the flat file is probably the one
requiring serious transformation).
Thanks for reading!
|