Overview of Service Fabric | Azure Friday at Build 2018

Overview of Service Fabric | Azure Friday at Build 2018


>>Yes. Hey friends,
I’m Scott Hanselman. It’s another episode
of Azure Friday. Just take a second
to have Jameela, turn around and show
the people behind us we have a massive
studio audience. They are in no way interested in the recording that I’m
doing of Azure Friday. They’re instead here
for free stuff. There are T-shirts, and
swag, and IoT buttons. They don’t care about us at all, but what we do care about
is Azure Service Fabric. I’m here with Matt, who is going to tell me
about what they’re showing today at the show here at
Bill, how’s the going?>>Doing great. We’ve got a lot of cool stuff coming
out of Bill this year. There’s lots of updates to
standard Service Fabric, but most of that is incremental. What we’re really
showing is some of the new stuff that
we’ve been working on. There’s two things that
we’ve announced now. One is, Azure
Service Fabric mesh, which is something we’ve been working on, and
we’re really proud of. It is server list fabric.>>Server fabric mesh.>>Yeah.>>Fabric is kind of
like fabric, right? And then, mesh is like
another kind of fabric?>>Yeah,it’s a fiber of fabric.>>Does it make
the fabric more meshier?>>Yes, absolutely, 100
percent more meshy.>>Okay. With Service Fabric.
What does that mean? Well, in Service Fabric today,
when you set up a cluster, you have to manage
a bunch of nodes, you have to manage a bunch
of VMS and machines.>>Well, you have to know that Service Fabric is the thing.>>Right. Yeah, you start there, but then you get into
the set up thing where even in Azure, Azure helps you out
by like deploying server fabric bits
on the machines and standing up to
cluster for you. But then, you as
the customer still have to deal with VM skill sets, and making that into
all sorts of water together.>>Yeah, the infrastructure
leaks out a little bit.>>You’ll still see it. For some customers
they like that power, but for a lot of customers that’s just overhead that
they don’t care about.>>Is this Service
Fabric Azure service?>>Yes, pretty much.
We finally got there. So, what you get at
the end of the day is you get all of the same
Service Fabric functionality, but you don’t have to manage
that cluster environments. So, Microsoft is running a giant Service Fabric
cluster for you. Then, you’re just deploying
your applications anyway.>>So, what kind of
things do you not have to worry about that you had
to worry about before?>>Well, like you
don’t have to worry about, say for example, you wanted to isolate
your services in a network, so that this service couldn’t poke out to
some other service, or talk to something else, and shouldn’t have access to it. Doing that before
was like very hard, because you had to figure
out where it was running, and set up the network
appropriately. It was very painful. Now,
that’s just automatic, where when you deploy
the application it’s automatically in
its own little isolated network.>>Nice.>>Another example is
like in VM skill sets, you still have to kind of set up, and think about how you want to do operating system patching. Do you want Azure to do it for you? Do you want to manage it? What gets deployed
when all that’s gone? Because you don’t see
the operating system, it that’s all just hidden. So, there’s a bunch of things
about like resource sizing, figuring out how and where
to run your applications, what type of hardware needed, wiring up all of
this infrastructure, all of that just disappears.>>And to get this slider bar.>>Yeah. All slider bar, it’s just one big
gooey slider bars.>>Do you have any cool demo
to blow my mind with?>>Not at this time, well, I mean there’s there’s
one running here. The neat thing about it
is that it disappears. I think it was cool in
Scott’s keynote yesterday, and such as it where he said, “The best technology disappears.”>>Right.>>So, this is actually
right in line with that where we’re taking
some of the hard parts of Service Fabric, where previously you
had to make all of these choices, and getting
it out of your way. So, you get to focus
on your application. Whereas previously,
you had to like define all these big
complicated XML models, and this multi-layer,
application packaging scheme. Now, you just get kind of a
symbol of YAML or JSON file, and you hand that to mesh, and mesh goes out of
this container image and it needs this many cores, and there’s many
resources, and here’s the network that hooks it
all up, and you’re done, and you have your web front end, and your staple service back, and deployed just like you
would in normal service ever. But, I didn’t have to
go through all that infrastructure, and
cluster management.>>So, what does this mean for existing customers
of Service Fabric? Can they enable this and turn around and
it just gets better?>>Yeah. So,
the first thing is that, almost all of
the mesh capabilities and Service Fabric mesh
are going to be present in the core
Service Fabric products. So, if you have
Service Fabric standalone, or Service Fabric
deployed in the clouds, all of those mesh
capabilities are still going to land in that product. So, you’ll be able
to have that same simplified application
description model, you’ll get all that
same network isolation features, all the auto scaling. So, all that’s going to land in the in the cluster proper. So, you’ll be able
to take advantage of it, For existing customers, there’s also going to be an opportunity for you to
think about whether or not you want to kind of
shift to the new model, and maybe take applications out of the clusters that
you’re running in today, and move them into mesh, so that you get rid
of that overhead of management that you
have to deal with today.>>So, you do get the
best of both worlds. If you’re someone who wants
a manual stick shift car, because you get more power and more flexibility, that’s great. If you want to upgrade,
or move laterally.>>Right.>>To an automatic shift car, that’s cool too. Now,
you have two choices.>>Exactly, and we really see that there are some
particularly in Service Fabric standalone where sometimes it gets deployed into highly regulated
environments, banks and the like, where there are not maybe comfortable with
the public cloud yet, or we’re already invested in
a lot of on premise hardware that they have an investment in and are going to
maintain for a while, or it’s customized in
some way for their workload. That’s great opportunities for
Service Fabric standalone, but I still want auto scale
of the application tier. So, their application
developers can focus on developing and deploying
the application layer, and then you might still
have the guy who is tasked, the IT guy who’s tasked
with making sure the cluster stays up and running. But then, if you wanted
to, you could take that same application description
and deploy it to say, dev test labs in Azure, or any other Azure environment, because the same descriptions in the same packaging
work everywhere.>>Very cool. So, where
can all the IT guys and girls go to learn
about this online?>>Well, we’ve got, they took my handouts but,
basically if you just go.>>Here are your handouts.>>Yeah. If you just go
to the first one is, the Service Fabric Mesh Preview. This is this is
old school printed out paper and focus on it. But that’s a great
learning page to tell you more about
Service Fabric mesh. There’s also great
information that comes out pretty regularly
on our team blog. The team blog also has a really cool thing where
every now and again, we announce our
community meetings. So, we have monthly
stand up meetings where people on
the Service Fabric team get on a Skype call, and anybody can dial in, and ask us questions, and hear about the updates that are coming to
servers fabric. So, those are announced the third Thursday
of every month. But those are announced on the blog as well exactly
what day and time. That’s a great way to stay in touch with the
Service Fabric team.>>So, it sounds like this
is a great opportunity, and a great time
for people to jump into the Service
Fabric community?>>Yeah. I mean if
you were daunted by all the work and set up that
Service Fabric had before, where you didn’t really sure
if you wanted to manage, to care, and feeding
of your own cluster.>>Yeah.>>But you were interested in
some of the functionality. Now, it’s a lot easier to
dabble and play around with it. And also, you don’t have to take on that side of the work
if you don’t want to.>>Cool. I’m learning all
about Service Fabric, here on Azure Friday, on the go.

2 Replies to “Overview of Service Fabric | Azure Friday at Build 2018”

  1. This is not a great video on what is Azure Service Fabric is…or even what service fabric mesh is…
    And hidden abstraction is something as a customer I want to see. as long as it works…but not as a developer because it means you can't do anything

Leave a Reply

Your email address will not be published. Required fields are marked *