2 ms·
> But when loom arrive every jdbc existing code will magically, automatically become truly asynchronous such spring should come on the top 4 place. I know less
by gpderetta 6y ago
> But when loom arrive every jdbc existing code will magically, automatically become truly asynchronous such spring should come on the top 4 place.
I know less than zero about Java and Loom, but if I understand correctly loom enables first class continuation and seamless M:N threading.
But I do not see how that will help jdbc, (unless you have tens of thousands of db sessions); I understand that the power of the new libpq is the ability to pipeline queries and that won't magically appear without development effort.