Parting completely from these strategies (discussed in “Other Approaches” section), eSnap adopts a minimalist approach. To link distinct databases, the need to identify the commonalities amongst these databases is necessary. These common fields can be accessed directly either as a base table, or as a static query (view), or as dynamic query (select statement), or as a stored procedure. This information is the only requirement for eSnap to be able to bridge these databases. Once this information is collected, eSnap’s framework can perform automatic search on these databases.

For every referenced database, the developer will code a specific ASP page(s) (Active Server Page) that will retrieve the requested information. The coding process is simple, fast, and straightforward due to eSnap’s published set of API (Application Programming Interface) destined to speed up the development process and to reduce errors.

The minimalist approach shields the developer from any structural changes. The ripple effect of any change is confined to the page that references the database that has been altered. This enables the developer to localize the maintenance to a well-identified boundary. In addition, adding new databases does not require redesigning eSnap’s framework, only the adjunction of a new page (or pages).  As far as directories/files are concerned, eSnap handles them automatically without any programming effort.