Promote the Log4j API
@@ -32,6 +32,17 @@ The API for Log4j is separate from the implementation making it clear for applic
methods they can use while ensuring forward compatibility. This allows the Log4j team to improve the implementation
safely and in a compatible manner.
+The Log4j API is a logging facade that may, of course, be used with the Log4j implementation, but may also be used
+in front of other logging implementations such as Logback. The Log4j API has several advantages over SLF4J:
+1. The Log4j API supports logging [Messages](manual/messages.html) instead of just Strings.
+2. The Log4j API supports lambda expressions.
+3. The Log4j API provides many more logging methods than SLF4J.
+4. In addition to the "parameterized logging" format supported by SLF4J, the Log4j API also supports events using
+the java.text.MessageFormat syntax as well printf-sytle messages.
+5. The Log4j API provides a LogManager.shutdown() method. The underlying logging implementation must implement the
+Terminable interface for the method to have effect.
+6. Other constructs such as Markers, log Levels, and ThreadContext (aka MDC) are fully supported.
+
$h3 Improved Performance
Log4j 2 contains next-generation Asynchronous Loggers based on the LMAX Disruptor library. In multi-threaded scenarios
