* Logback's architecture is sufficiently generic so as to apply under different circumstances. At present time, logback is divided into three modules, logback-core, logback-classic and logback-access. * The logback-core module lays the groundwork for the other two modules. The logback-classic module can be assimilated to a significantly improved version of log4j. Moreover, logback-classic natively implements the SLF4J API so that you can readily switch back and forth between logback and other logging frameworks such as log4j or java.util.logging (JUL). * The logback-access module integrates with Servlet containers, such as Tomcat and Jetty, to provide HTTP-access log functionality. Note that you could easily build your own module on top of logback-core.

* Ease of use - The logger of tinylog is static, so it isn't necessary to create an instance of the logger before logging. * Configurable - tinylog can be configured by statements, arguments and/or a properties file. * Fast - tinylog is very small, so it's simple to optimize the logger's speed e.g. by precompiled patterns. The result can be seen in the benchmark. There tinylog was up to four times faster than the popular log4j! * Scalable - tinylog is thread-safe. So the logger can be used in multi-threaded programs without the need of locking. All log entries are always created and written as a whole. Running on machines with multiple cores, tinylog benefits from the additional cores. * Small - As the name "tinylog" implies, tinylog is very small. The tinylog JAR has a size of only 75KB!