An Example of Automatic Component Creation (File Repositories):
As files are uploaded to the server, by a lender or a vendor, links to those documents are maintained on the order, not the actual files. The file resides in a file repository and is accessed by a link on the order. As a repository grows and reaches a threshold, a new repository is automatically created. Any new files added to the order will reside in the new repository and all links to the old repository will continue to work. This keeps the size of a lender data-store to a minimum, maximizing efficiency and providing immediate searching results. As additional files are added to an order, the size of the order remains unchanged and performance is unaffected, because the files are not physically located on the order.
Using virtualization and blade server technology, we can share resources (Memory, Bandwidth, Disk Space) on-the-fly between servers, removing all hardware limitations. At the software level, scalability is achieved using a central directory, which controls a highly efficient set of connections between each individual component. Components can be located on the same physical server or on separate servers; in the same physical location or in different physical locations, and changing the location of a component is as simple as changing a single document in the directory.
The application was designed with no limitations. The architecture spreads the application across an unlimited number of components and hardware resources. As a component reaches a threshold, new components can be automatically created based on profile settings. All links to the old component from within the application continue to work and are unaffected by the change.
