If you benchmark JSON Schema validators in Java, one question matters more than it first appears: does the validator work directly on your Java object graph, or does it first force you through a JSON tree? SJF4J is built around the first path. That is why the recent independent benchmark work from Creek Service is interesting. Because SJF4J's story is not just "we are fast". It is: we avoid work that many Java validation pipelines still force you to do. An independent signal worth paying attention to Creek Service maintains an independent comparison of JVM JSON Schema validators: JSON Schema validator comparison Performance comparison What makes this benchmark especially useful is that it looks at validation from two angles: pure validation against the JSON Schema test suite serde-style workflows , where data is serialized, validated, read back, validated again, and deserialized The first tells you whether a validator is strong at validation itself.…