Will Sargent
tersesystems.com · Personal blog · on HN since 2010
Will Sargent writes about JVM security, cryptography, logging, and production debugging, mostly in Java and Scala.
What HN saysHN links it for posts on Java security and queryable logging, and one commenter cites it when discussing binary encodings for logs.
23HN people shared it
1linked it in comments
31stories submitted
248story points
3 years agolast shared
2010people per year2026
Most-shared posts
- 1Developing in Production4 people · 10 points · first shared 2020 · 1 comments on HN
- 2Targeted Diagnostic Logging in Production3 people · 7 points · first shared 2019 · discussion on HN
- 3Effective Cryptography in the JVM2 people · 76 points · first shared 2015 · 10 comments on HN
- 4Fixing the Most Dangerous Code in the World2 people · 9 points · first shared 2014 · discussion on HN
- 5Listening to JVM Metrics with JavaSound2 people · 4 points · first shared 2020 · discussion on HN
- 6Closing the Open Door of Java Object Serialization (2015)2 people · 4 points · first shared 2015 · discussion on HN
- 7An Easy Way to Secure Java Applications2 people · 2 points · first shared 2015 · discussion on HN
- 8JSSE with Object Capabilities2 people · 2 points · first shared 2018 · discussion on HN
- 9Where Pair Programming Fails for Me1 people · 70 points · first shared 2010 · 38 comments on HN
- 10The Logic of Failure (2011)1 people · 40 points · first shared 2015 · 8 comments on HN
- 11Problems Scala Fixes1 people · 9 points · first shared 2012 · discussion on HN
- 12Monkeypatching Java Classes1 people · 2 points · first shared 2014 · discussion on HN
- 13The Right Way to Use SecureRandom1 people · 2 points · first shared 2015 · discussion on HN
- 14Latency and Throughput with Logback1 people · 2 points · first shared 2022 · discussion on HN
- 15The Right Way to Use Java.security.SecureRandom1 people · 2 points · first shared 2023 · discussion on HN
What HN people wrote when they linked it
wsargent · 2022-09-12
> I'm surprised this is up for debate.
I looked into logging in protobuf when I was seeing if there was a better binary encoding for ring-buffer logging, along the same lines as nanolog:
https://tersesystems.com/blog/2020/11/26/queryable-logging-with-blackl…
What I found was that it's typically not the binary encoding vs string encoding that makes a difference. The biggest factors are "is there a predefined schema", "is there a precompiler that will generate code for this schema", and "what is the complexity of the output format". With that in mind, if you are dealing with chaotic semi-structured data, JSON is pretty good, and actually faster than some binary encodings:
https://github.com/eishay/jvm-serializers/wiki/Newer-Results-on-Differ…