Yeah this is the positive side of the double-edged sword of frameworks.
Without Spring, you would have every team rebuilding the database layer in 100 different ways. With 100 shoddy attempts at documentation.
So for better or worse, having one framework-standard way to interact with the database, modify headers, or do any number of standard tasks makes life easier even if it enshrouds the underlying system in abstraction and layering.
Without Spring, you would have every team rebuilding the database layer in 100 different ways. With 100 shoddy attempts at documentation.
So for better or worse, having one framework-standard way to interact with the database, modify headers, or do any number of standard tasks makes life easier even if it enshrouds the underlying system in abstraction and layering.