[MUSIC]
>> Now I'd like to welcome
Microsoft Principal Architect for Java, Ed Burns,
Principal Engineering Group Manager
for Java, Martijn Verburg,
and Cloud Developer Advocate Julien Dubois.
Hey, welcome everyone. How are you guys?
>> Happy to be here.
>> Very well, thank you.
>> Let me start with you, Ed.
Actually, the three of you are Java champions.
There is actually many of you within Microsoft.
That could be surprising, but that's the case.
Ed, you used to work at Sun
on both the JSF and Servlet specs.
Can you tell us more about
the Java community inside Microsoft?
>> Absolutely, I'm very happy too.
You said the keyword Olivier, community.
For me, doing Java from 1997 onward,
it's always been about the community,
not just the people that are
in the core development environment,
but also the people that are building businesses on
top of Java and then going out and doing great things.
Inside of Microsoft, we have so many Java champions.
It's like you throw a rock, you hit a
Java champion, it's pretty easy to do.
But it's a very high-energy, exciting growth environment.
We're really excited to bring
the full stack of Java expertise
from the desktop to the IDEs,
to the frameworks, and to the tools.
>> We'll discuss some of that today actually.
Let me turn to you, Martijn.
One of the great recent announcements from Microsoft is
the release of its own OpenJDK Build.
Open source out there,
like freezing hell once again.
Can you tell us a bit about that?
>> Yeah. It has been a historic moment for Microsoft.
Whenever we go talk to the Java
ecosystem, when they hear that
Microsoft has released its own build of
Java with the Microsoft Build of OpenJDK,
it is a hell-frozen-over moment.
What we've done is we've released Java 11
a long-term service release that's been
battle-tested at LinkedIn on hundreds of thousands of
JVMs so you can be reassured it's production-ready.
We've also sneakily put out a release of Java 16 as well.
For the sharp-eyed amongst you who play
a small game called Minecraft,
if you take a look at the snapshot builds
and the version of Java running underneath there,
you'll see a very familiar household name that
you may not have previously associated with Java.
We're very excited to help out that community as well.
>> Do you think I should go talk to my 16-year-old who's
playing Minecraft every day about it? We'll see.
>> Absolutely.
>> Ed, Microsoft also announced
many improvements for Visual Studio Code for Java.
Could you give us an overview of what's new and
how this will ease the work of Java developers?
>> Absolutely. We talk
about Cloud-native and high-velocity.
These are two things that
Visual Studio Code does really well,
where Cloud-native in the sense of code spaces
being integrated into the Cloud with you,
and also the SSH-enabled remote debugging.
If you need to do debugging into
the Cloud worker node inside
your Kubernetes cluster working inside the pod,
you can easily pop into Visual Studio Code
and get right on there in with the JVM.
One of the things I loved about
what we're doing in Visual Studio code is,
it fits with the
idiomatic Java native way of doing things.
It's not only Cloud-native,
but it fits the way Java developers
expect things to work.
Because people have been doing stuff with IntelliJ,
with NetBeans for a very long time,
and these tools have
a very Java-native way of working. Visual Studio Code,
being a polyglot platform,
had to do some melding to fit that,
but it's actually gotten a lot better over time and
the Maven support is totally first class now.
>> Nice. So basically meeting developers where they are.
Making sure they are comfortable with their tooling,
with their frameworks, with their habits,
not changing all of that.
Martijn, actually - now, I want to talk about SDKs.
You are working on the Java SDK.
What are the current evolutions of the SDK?
What's going to happen in next year
or so? What's to expect?
>> Yeah, there's an awful lot going on.
My own contributions have been very modest.
My group has helped look after some
of the performance aspects of the SDK.
But I've had the pleasure of working with Jonathan Giles
and his incredibly experienced Java team.
The major change, to go back
to Ed's point, is idiomatic Java.
If you are now using the Azure SDK,
the Java version, you are
writing and you are using idiomatic Java.
It's a much more pleasant experience
for Java developers today.
Jonathan and Kerr have also dramatically increased
the amount of Azure services that the Java SDKs touch,
everything from managing third-party APMs
in your Azure subscription such as Datadog,
connecting to Azure Key Vaults, Azure sign-ups.
The list just goes on and on.
You really do have full coverage of
the entire Azure suite now with Java, which is fantastic.
>> Love it. Julien, I've not forgotten you.
You are a developer,
you're the Hipster actually,
if someone actually has been using JHipster,
you're the man behind that.
Julien, as a developer yourself,
one thing that's really great about
this SDK is that it's fully reactive using Project Reactor.
It's the same technology that
powers the new reactive spring.
So it becomes trivial to do
fully reactive Spring Boot application
using the Azure SDK.
What else can you tell us about Spring?
>> Yes. Thank you. Yes, it's a good time to
be Spring developer on Azure.
Spring is a framework that most Java entrepreneurs,
developers use so at Microsoft we fully support it.
What gets me more excited today is Azure Spring Cloud.
It's our platform as a service offering
that is jointly managed and operated,
with VMware, the makers of Spring.
We've announced quite a few new features, of course,
with supporting the Microsoft Build of OpenJDK,
we're going to have full support with our new Java agent.
That opens the door to a lot of new features on credibility.
Azure Spring code is all about developers gate-pushing
that code towards the Spring code and
us managing and running it.
We are bringing two new features
to Azure Spring code, which I really like.
It's bring your own Cortana,
so you bring your own Docker image.
Typically you can bring GraalVM
image if you want to do a Net build.
We're bringing small instance, 0.5 CPU instance.
That means we're going to work a lot on scalability,
so you pay less when you don't need it.
Of course, you scale
as much as you need, thanks to Azure Spring code.
As a developer, you get to have
a great experience and good scalability out of it.
>> Awesome, thanks, Julien.
One more thing I'd like for you
to share with our audience here is,
is there anything particular at
Build this year you recommend people to go check out?
>> Well, I think all of
the Java-based content is super exciting this year.
We have an ask-the-experts roundtable at
the end of the day today
that I think you should check out.
>> Well, that's perfect.
Ed, Martijn, Julien, thanks a lot for joining us today.
Well, I hope you enjoyed the event as well.
To all the Java champions around, well,
we have some of you at
Microsoft and would like to make the tools
that you're familiar with and you
like the best of breed over here.
Thanks, guys, for joining us today.