Комментарии:
super super clear. 👍
ОтветитьLogback, SLF4J and Log4j2 are Java logging frameworks. Logback is an implementation with a facade API, SLF4J is a facade for various logging platforms, and Log4j2 provides both a facade API and an implementation. They all aim to provide a standardized API for logging in Java, allowing flexibility in how you choose to actually implement logging.
ОтветитьExplained very well
Ответитьbeautiful thanks❤
ОтветитьHow to become good in coding?
ОтветитьSFL4J API or Log4J2 API ?
ОтветитьExcellent !
Ответитьthat was awesome! thank you.
Ответитьapparently choice is hell.
ОтветитьBecause Java...
ОтветитьI think fine is not that FINE the debugger level, but it means the granular logging, which means every single piece of information will be logged when logging level is fine.
It contains more sensitive information's and we normally use it when debug or info level logs are not worth analysis.
I should also add that both past experience and recent events suggest to me that no one should use log4j2. If you understand the recent security problems you'd have to conclude that the team involved didn't understand that it was a bad idea to (BY DEFAULT) scan log messages looking for special char sequences and then potentially download and execute remote code based on it. This suggests they don't understand basic security or performance concepts, but also that they don't know that most people won't want all kinds of random and obscure features thrown into their production system, where it would take a lengthy read of docs and/or code to even know what you're getting!
ОтветитьHelpful
ОтветитьLog4j1 was before jul
ОтветитьI want to say something to you Kaushik, I am new to development (less than 1-year experience) currently working with an IT company here in Pakistan as a Java developer, but let me tell you When I get a job in Europe I will surely donate too much money to support your channel. Love for you Kaushik sir! 😄🥰
ОтветитьHi Sir I have question here,
Even if a .class file enters log what that can do, because it will be on log files, how can hackers can execute java from a log file.
May be I'm silly but I got this doubt
"what is the difference?": One of them had a major vulnerability that affected a big part of the internet to be at risk. But I'm not telling which one it is...
Ответитьrofl
ОтветитьWatching this again after the Log4J2 incident. Logging hell gets a different meaning.
ОтветитьGood video, but I would challenge your assertion that logging is a mess. Keep up the good work
ОтветитьI'm from the future, in December 2021 Log4J will, oh god, I've said too much!
ОтветитьLogging really became a hell with log4J🥴
ОтветитьPlease use dark background in you presentation 😂
ОтветитьThank you so much
ОтветитьUp vote for speaking truth! Logging Hell!
ОтветитьKing <3
ОтветитьYour channel is all what every enterprise Java developer ever needs
ОтветитьThe history part was basically wrong: Java util logging came AFTER log4j.
Basically log4j was the first widely adopted logging framework in Java, and later Java borrowed the idea (hierarchical logger, log level, appender/handler) and make up its own logging framework (java.util.logging)
The part for log4j2 was wrong too: right slf4j was developed as a facade. And logback was developed as a “native” implementation for slf4j almost at the same time slf4j was introduced (they are from the same guy anyway, which is the original author of log4j)
Log4j2 is basically the same: it contains the API part (which is basically what slf4j) and implementation (just like logback). Which means you can use log4j2 API and use slf4j/logback as backend.
How do you come up with so much clarity? The video seems to be short, but the effort you would have spent going through their docs and understanding, then coming up with just the information required in 10mins is tremendous. Respect.
ОтветитьFound the answer after a long time
Ответитьvery good job, thank you
ОтветитьThat thumbnail though hahahaha
ОтветитьGreat video! Thank you for this clean explanation.
ОтветитьJust one question, little bit off the topic related to design(i am learning these days). Why Facade, why not adapter ?
ОтветитьSuch an informational video, which is not even covered in paid courses.
ОтветитьGood content ! One thing I'd like to add here is SLF4j vs log4j is that placeholder { } in SLF4j reduces lot of string concatenation in the code and also avoids creation of String Object, thereby reducing the memory requirements , and this could be handled by if (LOGGER.isDebugEnabled()) clause in log4j style.
ОтветитьThanks sir for explaining in detaills
ОтветитьI have programming for many years and don't know this, I feel like a loser.
Ответитьawesome comparison.
ОтветитьMyself am a noob in java and I would cry for real if i am asked to
work on logging.Thanks alot man.
wowww dude this cleared a hell lot of stuff.. thanks for this..
ОтветитьExcellent tutorial. Thanks a lot
ОтветитьCan you do one on OpenJDK?
ОтветитьWhat we need is to consolidate all the frameworks into one. The authors should get together and merge the best features of each into one. Same with the major frameworks.
ОтветитьSupremely digested, thank you so much! I might add, as well as the other videos. You're making a great contribution to the developer society. Very informative and very ingestible.
ОтветитьI came knowing nothing about logging libraries now I know you can have multiple libraries serving your project! Thanks man!
ОтветитьMan I love your Intro!!
Ответить