One for general certificate management, then an adapter for the specific certificate format, then another instance to do the cryptography, and then one for the signing.
Compare this to .NET, for example, and it's far more use case oriented. You want to sign some data? Here's a class and method that does it for you. Oh, and it's static.
And, I think newer Java developer get it: they usually design their classes for ease of use, not some abstract design quality metrics that nobody cares about, some obscure OOP metric.
Right, because the JDBC is exactly how I described above: you need to instantiate half a dozen skeleton classes that you then instantiate with a hundred adapters, before you can execute a single SQL statement.
It will not only give you the results, it will also render them in a Jupyter notebook, put a bow on it, and hand deliver it to your grandmothers log cabin in the woods.
