Obviously, there is huge performance gain
by replacing three LDAP operations with three lookups in a local memory object. Reusing
the application data source to build the data structure alleviated any additional work from
the corporate LDAP directories.
Caching lookup tables and other relatively stable areas of the database is easy and reduces
the workload on the database and the application. It is a simple way of maintaining the user
experience while improving performance.
Dynamic Table Data Cache
Static data is an easy and obvious caching opportunity, one that many architects and developers
can easily apply to existing or new applications with very little investment. Obviously,
things get challenging when caching occurs at the application layer, and the data has the
possibility of being updated. Suddenly, maintaining appearances to an end user has to be
well thought-out.
With the move to a modern Web application, IBM??™s expertise location exposed several
common services and introduced an unexpected load. Caching at the service layer played
a very important role in sustaining the growing popularity of service-oriented architecture
and Web services.
In this type of cache, we need to deal with a table data which gets updated continuously by
the Web application.
Pages:
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313