Re: Modernising a monolith ile program

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Caching makes the most sense when the data comes from a file....

Reduces the number of I/Os your code needs to perform...

I usually store a time-stamp of when the data was retrieved, after a
set period of say 15 seconds, I'll re-retrieve the data.

This allows for single purpose procedures Customer_isValid(),
Customer_GetName()...without an I/O penalty.

Sure, the data could be stale, but no worse than an old school
monolithic program that read the record at the beginning of the
program without a lock and used the data throughout the program.

Charles

On Fri, Jul 1, 2011 at 10:25 AM, James Horn <jdhorn@xxxxxxxxxxxxxx> wrote:
> Hi Pete
>
> The caching seems a little scary to me.  I assume you don't do it if the
> method gets data from a file (or whatever) which could change between the
> calls.
>
> Jim