Project Loom, Fibers, Oracle stopping work on ADBA

--000000000000ab42a205935435b3
Content-Type: text/plain; charset="UTF-8"

Hi,

I just saw the announcement in the JDBC spec email.

Oracle has stopped work on ADBA due to Project Loom adding Fibers to the
JVM/JDK.

*> We stopped work on ADBA for two reasons: per the Java team the future
for scalable Java code is fibers, not async and there was very little
support within the Java community for ADBA. The announcement was made at a
CodeONE session on scalable and asynchronous database access. The only
person in attendance who was interested in ADBA was in fact happy to learn
that we had stopped work on it. His interest was primarily concern about
the work required to implement it if it became a standard. The Java team
stated that ADBA would never be accepted as a Java standard as it was an
async solution to a problem that would be addressed by fibers. Unless it
became a standard ADBA would have very little impact, certainly not enough
to justify the effort.*

Project Loom has the effect of making *anything* using standard Java IO and
Java Locking non blocking so for myself this isn't a surprise at all.

That is, the expectation is any Type 4 JDBC driver will effectively become
non-blocking (of OS threads) when Project Loom gets into the JVM and JDK.

I just thought this was interesting news to share in case people had not
been following Project Loom.


Cheers, Rob.

--000000000000ab42a205935435b3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>I just saw the announcement in the =
JDBC spec email.</div><div><br></div><div>Oracle has stopped work on ADBA d=
ue to Project Loom adding Fibers to the JVM/JDK.</div><div><br></div><div><=
i>&gt; We stopped work on ADBA for two reasons: per the Java team the futur=
e for scalable Java code is fibers, not async and there was very little sup=
port within the Java community for ADBA. The announcement was made at a Cod=
eONE session on scalable and asynchronous database access. The only person =
in attendance who was interested in ADBA was in fact happy to learn that we=
 had stopped work on it. His interest was primarily concern about the work =
required to implement it if it became a standard. The Java team stated that=
 ADBA would never be accepted as a Java standard as it was an async solutio=
n to a problem that would be addressed by fibers. Unless it became a standa=
rd ADBA would have very little impact, certainly not enough to justify the =
effort.</i></div><div><br></div><div>Project Loom has the effect of making =
<i>anything</i> using standard Java IO and Java Locking non blocking so for=
 myself this isn&#39;t a surprise at all.</div><div><br></div><div>That is,=
 the expectation is any Type 4 JDBC driver will effectively become non-bloc=
king (of OS threads) when Project Loom gets into the JVM and JDK.=C2=A0=C2=
=A0</div><div><br></div><div>I just thought this was interesting news to sh=
are in case people had not been following Project Loom.</div><div><br></div=
><div><br></div><div>Cheers, Rob.</div></div>

--000000000000ab42a205935435b3--