Each application developer faces the problem of logging usage information. On
the one hand, the more logging that's done the easier it is to detect and
locate the source of problems. On the other hand, large volume logging might
impair an application's performance.
This problem is typically solved by defining various log levels dependent on
a program's maturity. For example, a program in developmental stages would
have a higher logging requirements; logging requirements would be relatively
lower in the production phase. If an application requires a lot of logging
for audit purposes, then special measures are required to protect
performance.
This article provides a possible solution for this problem by using Spring
asynchronous support.
Rationale for High-Volume Logging
Logging is used extensively to help find problems within applications. A
developer who finds a p... (more)