>
> #3) Specific to algorithmic complexity - it appears that jobs are
> keyed by ID, yet accessed using a sequential search [1] - this does
> not scale well to large numbers of jobs.  Is there no better approach?

The expectation is there is large amount of data, but the number of jobs
are not that large.  Say we run a reporting job every day, it is still
one single job with many JobInstance and JobExecution.  So I think the
sequential access is acceptable.  I guess another reason I didn't want
to maintain a mapping is I really don't want to duplicate the job id as
the key.

I'm not sure what you mean by " I really don't want to duplicate the job id as

the key".

The map key is already contained in the associated map value, IOW, using a field of the value as map key.