Criteria for Metrics

enaio® • 11.10 »

Consider which of the following criteria apply to your application scenarios in the entire enaio® system (and to what extent they apply): We define applications as clients, core services, or interfaces. This should allow you to create a diagram of the entire enaio® system, taking all the criteria described above into account, and to fill it with data flows and components. You should therefore also know the quantities and/or expected/estimated times.

  • How is the system being used? Is it used solely for storing data or for client searches? Or do users edit data in the system?

  • How many users access the application and start searches or jobs in it?

  • How often are jobs started (per minute or hour)?

  • What speeds are required?

  • What volume of documents does this entail (in GB, volume/hour, day, unit of time)?

  • Is the volume in a queue? Is asynchronous processing possible, or do users wait their "turn" for the results?

  • Where are bottlenecks expected? (In addition, does the application have to first fetch the data from a remote source which has a slow connection?)

  • Are there peak load times? Are the same application response times required at both high and low loads?

For which object types in enaio® do

  • page numbers,

  • previews,

  • thumbnails,

  • and text extracts,

need to be created by enaio® documentviewer?

Taking into account the criteria specified above, you should now create a diagram of the entire system and fill this with data flows and components. The quantities and/or times should also be known.