Re: Project Loom, Fibers, Oracle stopping work on ADBA

Dave Cramer <[email protected]> Wed, 25 Sep 2019 08:25:46 -0400
Newsgroups gmane.comp.db.postgresql.jdbc
Message-ID <CADK3HHJXbg3OhVsJDneLRki2PKnns82xuCHg-_KMxAm4Gsk2xQ@mail.gmail.com>
--0000000000004b0fb905935fc1f1
Content-Type: text/plain; charset="UTF-8"

Hi Rob,

I had seen the announcement.

Interesting. I'm curious when they expect loom to be mainstream?

Dave Cramer

[email protected]
www.postgresintl.com


On Tue, 24 Sep 2019 at 18:39, Rob Bygrave <[email protected]> wrote:

> 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.
>

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

<div dir=3D"ltr">Hi=C2=A0Rob,<div><br></div><div>I had seen the announcemen=
t.</div><div><br></div><div>Interesting. I&#39;m curious when they expect l=
oom to be mainstream?</div><div><br clear=3D"all"><div><div dir=3D"ltr" cla=
ss=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr">=
<div>Dave Cramer<br><br><a href=3D"mailto:[email protected]" target=3D=
"_blank">[email protected]</a></div><div><a href=3D"http://www.postgre=
sintl.com" target=3D"_blank">www.postgresintl.com</a></div></div></div></di=
v><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"=
gmail_attr">On Tue, 24 Sep 2019 at 18:39, Rob Bygrave &lt;<a href=3D"mailto=
:[email protected]">[email protected]</a>&gt; wrote:<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex"><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 due 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 future for scalable Java code i=
s fibers, not async and there was very little support within the Java commu=
nity for ADBA. The announcement was made at a CodeONE session on scalable a=
nd asynchronous database access. The only person in attendance who was inte=
rested in ADBA was in fact happy to learn that we had stopped work on it. H=
is interest was primarily concern about the work required to implement it i=
f it became a standard. The Java team stated that ADBA would never be accep=
ted 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 li=
ttle 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 stan=
dard Java IO and Java Locking non blocking so for myself this isn&#39;t a s=
urprise at all.</div><div><br></div><div>That is, the expectation is any Ty=
pe 4 JDBC driver will effectively become non-blocking (of OS threads) when =
Project Loom gets into the JVM and JDK.=C2=A0=C2=A0</div><div><br></div><di=
v>I just thought this was interesting news to share in case people had not =
been following Project Loom.</div><div><br></div><div><br></div><div>Cheers=
, Rob.</div></div>
</blockquote></div>

--0000000000004b0fb905935fc1f1--