What are disadvantages to use ServiceStack.Logging.NLog instead of direct NLog calls? -


i nlog due multiple reasons described in https://robertmccarter.com/switching-to-nlog and

log4net vs. nlog

however consider   https://github.com/servicestack/servicestack and https://nuget.org/packages/servicestack.logging.nlog keep generic interface , ability switch other provider in future.

is aware disadvantages/limitations of using servicestack.logging.nlog  instead of direct nlog calls?

will cause essential performance degradation?

is functionality available when called nlog loggers directly, not supported by  servicestack?

i've compared   servicestack ilog  , common.logging/ilog   and   nlog/logger.cs , found nlog has bigger number of overloads, make more type-safe. also nlog has logic  not process formatting if logging particular record disabled. 

based on decided using generic logging interface yagni. if write library used in multiple applications potentially different logging library used,  servicestack is way go.

however in application development no immediate need support more 1 logging framework, more efficient call nlog directly. if in future it would be decided switch other provider, global replace changes call  servicestack or directly new provider should relatively easy.


Comments

Popular posts from this blog

How to mention the localhost in android -

php - Calling a template part from a post -