Videos

language: EN

                  WEBVTT
So this is like a policy account that you create and you decide what can be done with the resources of my cloud.
And who can do that? And that is the full field of the directories.
Ok, so as I told you, my name is Andrés Mujica. I will be the trainer in this course.
Ok, so that was our environment. We are going to use some of that stuff there.
And what we are going to do is, well, we already did that, is we are going to create an Azure account.
So I can show you what we want to add here.
So let's see. So we are going to, we will be the last number two, or one, the previous one was the last two.
So here we are going to just check if we have our subscription.
So here is the purpose of the setup. So what we want to do here is to access the portal of the account.
Here is the account.
Then you can do it outside.
So as we are going to do this later.
Absolutely. Yeah, absolutely.
Yeah, you can create a free, I mean, ok.
Actually, you can, with the corporate account, you can create a free subscription and use that one.
Or you can have a personal account and create a free subscription with a personal account.
And I do agree with you that the corporate subscription will not be used for training.
And to the comments that we are going to do. So be aware of that as well.
I want to show you really how to create this free account here.
So in this link that I sent you guys, there is this option. You have three ways to use it.
So this is what is offered here. And the start-up option will give you the option to create a free account.
So let's move on. When we reach the last, we can see there.
We are going to provision some of the subscriptions.
So let's move on. So the first thing that we are going to discuss is something called the cloud adoption framework.
So there is, actually let me drop to this slide.
So this gives you the business strategy.
So it will give you one way to do this, a unified way to do it.
And how to motivate or how to align the adoption of the child with the requirements of your business.
Which outcomes you expect. And allows you to process all through this adoption lifecycle.
This cloud adoption framework has several steps. The first of them is the strategy.
This strategy is why are we moving to the cloud?
Why are we moving to the cloud?
Regarding the business. And how should we do the free system?
How to solve the chicken vs. egg dilemma here.
So which product to choose in order to navigate to the cloud.
After the strategy is done, there is a set of steps which usually are, I mean, you cycle around these steps.
Regardless of those projects that you choose to move on.
And these steps are the plan, the planning stage.
So this will be the slide.
So this is six. Yeah, this is six.
So this first one is the Microsoft Assessments.
So here you can see the different assessments that are available.
They will be here for example, for help with you.
So depending on the stage that you are within the cloud adoption strategy or framework.
You can choose which assessment to do.
So this is a full framework that gives you a hand guide you in the process.
Super valuable. So in this case, we would want to do the cloud drawn tracker.
And then took this stuff.
So this cloud drawn tracker, it just takes about 15 minutes.
There are multiple choices and multiple response.
So this will give you a result at the end.
So you can have some guidance on how to act and what steps to follow.
So please let me know if you are able to access this.
And I would recommend you to sign in.
Because you will be able to save these results.
Because remember that the idea that after a while you will see this and see if you have closed the gaps.
That you can type in this first tracker and work with that.
So saying that let's have this in the mix so we can execute the cloud drawn tracker.
You can save this, give this a name.
So go ahead and give the name that you want.
I'm going just to give it a name here.
And we can have these 15 minutes.
Feel free to ask any questions.
I'm going to do this with you.
To do it by yourselves for the first 10 minutes.
And after that, I will just jump in to discuss the questions that you have here.
Depending on what you would like here, it will change the other options that are available.
I'm going to shoot the second option.
So let's say that I'm already sold into Azure but I'm just starting.
So to see how this works.
So there are some more additional questions.
Which are important.
For example, sometimes going into the cloud, it's a response to a critical business.
For example, there was a ransomware attack within your company.
So, okay, you need to start over again.
And that is the strategy one.
So regarding plan, and I'm going just to, I'm not going to go into all of this.
But the ideas, I think that you have the ideas here.
Because these two is something that you may want to do with your customers.
Or within your own company.
Because this gives you the general process.
So let me go back here.
So I can show you.
When you finish this process, you will have a resource page.
So this will give you an overall result of how are you scoring against a specific category or a specific step.
And how do you need to improve.
So we are talking regarding customers.
So this assessment will provide you with several actions to act upon it.
And that's it.
This is like the guidance that you can use.
So this is the cloud on cracker.
Let me know please if you have any additional or any questions available as well.
This can be exported, right?
Once you finish this, this can be exported as a CSD line.
That can be later be imported into another platform, into a project file or just in the south of the forest as well.
So that is the cloud on cracker.
It takes a while to discuss and to create a role.
But it's like that baseline that is important.
Let me know guys if you have any questions.
If any of you finish the whole assessment and want to share the results, that would be super cool as well.
Let me know if any of you guys have it or want to do it.
So we can do it.
Okay.
So as we have discussed in this webinar, we discussed a lot about it.
But there is these four items which are super important.
The motivations, the justification for the business, the outcomes for the business that we have at the end of the process.
And okay, cool.
This is, let's see, this is where it's going.
These are the overall results.
Okay, super nice.
Five of ten.
Moderate.
Thank you for sharing.
Oh, there is another one here.
And this is, yeah, I mean, this is like the real life.
You can see if you guys are seeing what is being shared in the chat.
So yeah, usually that is the starting process.
There is a lot of stuff to work on.
And that is the idea.
That is where this assessment comes from.
Awesome. Thank you.
And there is an item here that allows you to identify the first project as well.
Oh, let me see.
Okay, this is like super simple.
Thank you for sharing.
So this identified that first project is a super nice way to step into the cloud adoption journey.
So this is the incremental approach that usually there is like a subset of applications that you start moving into cloud.
So that is like not going to everything at once.
But you start with a first project.
Once that is done, you have like execute all this stuff.
Regarding this last plan.
So you need to close the gap.
Here we are going to do our next lab, which is the creation of a cloud adoption plan generator.
Because this tool, what we are able to do is to have, let's say, like a template for a cloud adoption plan that we can use.
And we can adapt to our needs.
And it's super useful.
And it leverages all the stuff available to you within Azure High School.
So let me go back to the virtual machine that I showed.
And please let me know if you have any questions so far.
And they work like so.
So this goes here to this.
You are all.
So we are going to system.
So how are we doing?
Any of you have any issues?
Here, this place.
So if you need any help getting into this location, let me know.
So here you choose a template.
You will find a lot of options.
These are super nice.
I mean, I highly recommend you guys to take the time to check on this because these are super cool.
We really, really good templates so you can work, play, learn a lot.
So all of these are super nice.
So there is one that we are going to use here for this training.
That is the Cloud Adoption Framework templates panel.
So here you will find multiple templates.
Multiple templates for the Cloud Adoption Framework.
So this one, the Cloud Adoption Framework, the one that we are going to do right now,
before going there, let me talk about the others.
So this is the Cloud Adoption Framework, which is our lab format.
But there is also this cap, this full cap, which is a checklist that is complemented to the assessment that we just did.
Because this covers the whole cap framework.
This is another for several iterations that allows you to execute them in a great part of the strategy.
The red and the red part.
There is this one regarding Qubesnets, which is super nice because Qubesnets,
it's gathering or it's getting a lot of cloud all over the world and it's being adopted more and more.
So this helps you to adopt formats as well.
SQL migration, this is another hot topic.
A lot of companies in the United States take cloud databases and usually this creates a lot of fear.
It's okay to migrate the databases into the cloud, so this helps with that.
There are virtual desktops, which also work.
An important protagonist of the pandemic times.
There is some stuff regarding knowledge, the governance, the data warehouse,
the pay, IOT, secure, so secure research, governance analytics, those are other things.
So in this case, we're going to use the Cloud Adoption Framework.
So let's just select that template.
And here in Cloud Adoption Framework, we are going to deploy that.
So this create this, create a project for this.
This name should be unique across your organization.
So here I'm going to call this Cloud Plan, Azure Articat.
And the organization, in my case I have multiple organizations.
In your case, you have just one or multiple ones, depending on if you have ever used the apps or not.
Let me know if you have any issues there or if you have any issues, so I can help you.
So once you have this, create the project and we will take a while to create.
Not much, actually, but let me know if you have any assistance please.
No, not really, this is free.
And if it does, it won't accept.
It won't even raise you one dollar.
Because this doesn't create a machine or anything.
This is free.
Sorry, I wasn't able to see you.
Who talked to me? So you pointed to your machine.
Which one is it?
So share this screen so we can see from there.
Or just give a different name because perhaps someone else had that name and that is why it's calling it.
Dash, Jason, exactly.
And choose the organization.
Perfect.
What is it?
Oh, is this here to create your organization perhaps?
No worries, no worries.
This is the idea.
And you can create a new project, new organization.
New organization.
And actually I really recommend you guys to each one of you to have your organization for having a playground.
Because there is a lot of stuff that you can do with Azure DevOps.
And in my opinion, the best way is that you should have your own Azure account and your own DevOps so you can work with them.
Or you can convince your boss to write a subscription for you.
A small subscription.
I mean, it doesn't have to be a huge expense at all.
So you can be on top of that subscription.
You can create a payment directory for your own use and work with them.
I mean, this is super flexible and super powerful.
And all the demos that are in Azure DevOps are amazing.
Create an organization.
Oh man.
Oh.
Let me see.
No.
We can give it a try, Jason.
Let's give it a try.
Go to Portal Azure as well.
Because I see that you have a Visual Studio professional subscription.
That means that you have your own subscription.
Yeah, you have your own subscription.
So you can have, I mean, what we can do is that we can create a new directory for you.
So your own instance.
So yeah, you have a subscription.
You are the master of your domain.
There is no such.
Let's go to the upper corner.
The right one.
No, where your account is in Jason Delgado.
The top right.
And go to, let's view account.
Okay.
Organization.
Yeah.
Let's see what we have there.
Okay.
Okay.
No worries.
Go back to the Portal Azure tab.
Okay.
Okay.
No worries.
So we're going to create a new tenant.
And this is free and we can do that for sure.
Go back to the top left corner to the menu.
And go to create a resource.
Right.
Yeah.
Create a resource.
Create a resource.
And we create an entry.
Write down entry or active directory.
In the search box, you can just type entry.
Entry.
Entry.
Entry.
Entry.
Entry.
Entry.
If you want to share your phone.
That's fine.
No.
Yeah.
No, no, no.
Let's search for Azure Active Directory.
Instead of Active Directory.
Azure Active Directory.
Can you click on Azure Services only?
Just need the...
There.
Actually search.
The check is not.
There is a check box.
But there is Azure Services only.
Just behind the search box.
Right there.
Uh-huh.
Okay.
Now...
Oh.
It's not there.
Okay.
Let's go back to home.
Let's go back to home.
Go to...
I can see it either.
Let's go to the search box.
Look for entry ID.
Type entry ID.
Entry.
Entry.
There.
There.
That means it doesn't have an ESP.
But in the top, there is an ad sign.
In the top.
In the top.
At the...
At the...
Okay.
Let's go back to Chrome and Azure Services.
Because we need search for entry.
So perhaps that is why we didn't work with the Cs.
Let's look for entry.
Create the...
No worries.
No worries.
And...
Were you in the menu?
Go back to the menu.
Uh-huh.
And create a resource in the class sign.
And enter.
Write that.
Enter.
That's it.
Okay.
This one.
Fine.
Uh-huh.
Uh-huh.
So this will be a new tenant with your subscription.
And...
Oh, wait.
You don't have access.
Okay.
So we are...
Okay.
So yeah.
Only option then...
Uh-huh.
Uh-huh.
Uh-huh.
Is to create a free one.
Uh-huh.
Well, that's a shame.
Yeah.
No worries.
And if you guys, if any of you guys have the same issue, please leave the moment to do
that.
Uh-huh.
Uh-huh.
Uh-huh.
Yeah.
No worries.
So in the meantime, I'm going to go back to the...
Okay.
Perfect.
So at the end of that process, what you will end up with is...
With this project, this DevOps project that has...
I mean, not sure if you are familiar with DevOps, but this has like four or five components,
and host is just a machine that we put in the process.
So these are like the basics of...
Or like the first bits of the strategy.
And after that, we will have the...
What?
The...
Oh, yes.
That's...
First, the user stories.
So these user stories that...
So this actually points to the documentation and explaining which one of these...
Which one of these components that are here.
So this is the Quick Start Center.
So this Quick Start Center has the...
Okay.
It's like a checklist, a live checklist, which each...
Okay.
Let me...
Let me show it again.
Let me show you.
Okay.
I'm showing...
Okay.
So this is the Quick Start Center.
So this is a checklist, like a live checklist, or a practical checklist that you can follow
in order to create that language and sound by yourself.
So in this first lab, you get started with the actual protocol, which is like...
Create an account, create a free account.
You start architecting solutions, organize resources, select the actual region for your
deployment.
And this is like the first lab.
And later in the training, we will have this other part as well.
So I'm just going to show you how this works.
So this gives you like a brief explanation of what this works, what you need to do, if
you want to get deep in this step.
And that is like...
This is the way that this checklist works.
So it gives you like a guideline to work with.
And there are...
The most beautiful part is this, for example, in the architecture.
This is in the trainings.
We are going to see this workflow.
Because these decision trees allow you to define what to use for each one of your workloads.
So how to manage the storage.
So these are super useful.
So we do have those in here.
Or you can just go there and open this images and have a copy of those.
Because these, again, these decision trees are super useful for the compute design, for
the storage design.
So those are two parts of this process.
Also in the management of the organization, so how to manage the group, the subscriptions,
everything.
We are going to see this as well later.
How to select the regions for your deployments.
Because it depends on the geographical location of the resource of your deployment and the
location of the resource.
So this is the color of the framework that we have here that we have been discussing
this morning.
And this is the strategic integration system.
So this is kind of the same as before.
And similar to the one that we did earlier.
So I'm just going to show you.
But it's the same as before.
So this will take years.
I mean, it's not like one month or two or three months.
No, this is six months, one year or multiple years.
That takes a long time to fulfill.
Depending, obviously, on the size of your company or the customer's company.
So that is important to be aware.
So those are the iterations and the assessment of the deployment and the release of those.
There are some tools that can be used for the assessment for data for SQL Server.
The service integration, the Azure Data Box, which is super cool.
Gadgets to migrate data.
And you are talking about terabytes or petabytes of data.
And you want to move those to the cloud.
So this is just like an external disk drive that you can plug into your on-premises data center.
Copy of the data.
And once it's ready, you can send these back to Azure and they connect that to your workload.
And you have the data locally so you can copy that.
And it will save you a lot of time copying huge amounts of data across the cloud as well.
And the tools that you will need for the release for trust or advice regarding the waste and
critical workloads, the monitoring and the security center.
So we are going to talk a little bit about some of those.
There is another lab, which is the integration guide that helps you to create that integration setup process as well.
I didn't show you the digital studio capabilities.
But let me show you really really quick so you have an idea.
Because within this whole studio, within this whole studio, you can have digital IOR to embedded.
It's already installed in your environment.
But if you want to do that, you can do it in the digital studio in your website.
So this has almost 2 million downloads.
And it's qualified as a 5.
So it's a really good experience.
It's interesting to use that.
So just like an example, what I'm going to do is to open one of those diagrams.
So here we just show up the diagram as we work with the same tool.
So this is interesting.
So within the tool I use, the computation, you can see how everything can be worked out together.
So that is something that's really good for you.
For you, this is a good experience.
The CCO board.
So this is the CCO board.
So the first dashboard is the Azure Interceptor dashboard.
So this will give you all the information regarding their identity, their access control, their security of their resources, their networking information, their compute information, any results, any subscription quota, any links.
So the dashboard looks like this.
So it's actually like this.
So this requires a Power BI license.
What I'm going to show you.
So you can see where it is.
So what the only thing they need to do is to import the dashboard and link the Power BI to Azure so you can extract the information and have the right one.
So you can see what we discussed previously.
Usually, as I told you, this is usually just a group and a subscription because that is the most common way of employment, which again is not the recommendation.
You have a spectrum so you can do well over the time and have multiple subscriptions.
So this is the one that's one.
So you can show an easier way to the management and to the customers what they want.
Also, there is this infrastructure dashboard with dual nets.
So it has the information of the infrastructure as well.
And that is because two units is one of the five one process.
The sources within Azure.
So it allows you to do this.
And actually, we are seeing the advice for each one of the sources as well.
How this works.
This is the platform.
So we have this.
So we have a plan and get a copy of templates and these templates to Azure.
This is not with our license because.
Thanks for the application.
It also needs a witness to do this.
But let me show you.
So, in the.
So this first infrastructure dashboard explains how this works.
So these are all the.
So it has the deployment guide.
So it explains step by step what needs to be done.
So it's harder to have the dashboard deployed.
The power of the environment.
So it is not really complex to do that.
The license and the.
So you call it.
Absolutely.
Here is the process.
The link is in the slideshow.
The same with the government dashboard.
The process.
Are you going to come back?
It's to be done.
And the reports.
Everything.
What we're posting.
For each one.
You are going to go.
This is for.
This is for.
The standard.
The security.
The policies.
So this is.
The.
The.
This is the.
This is the.
That's what.
This one shows all the information.
So you are already using Azure DevOps.
This also will be super useful.
Because this will show you.
A status of the.
The DevOps.
So we show the.
To configure those.
The projects.
And then we request available branches, projects, deployments.
So that is super nice.
Here is another one for GitHub.
That is like the same for DevOps.
Remember that Microsoft.
So.
So.
So.
We are going to keep both.
Just to.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
So.
This is a set of tools.
Actually that is
within the
material of the training.
So, this is a set of tools
that allows you to
to use the tools
that allow you to use the tools
that allow you to use the tools
that allows you to
analyze
analyze
analyze
the performance
the performance
that gives you like
an ability to
test different stuff
in your platform.
In performance
and in work.
So, all of this stuff
shows you the tools.
These are the tools that are here.
This is a working product so it's not fully
finished but what they have done so far.
Actually it's kind of good.
So,
this is kind of
with the results of the review
that you were
exploring right now.
You can export that CSV file
to this tool.
And with that there is a PowerShell
script here that will take
all the information from that file that you created.
And it will help you
to create
a report
that you can use to show
or to gather all the information that is in here.
So,
I'll just show you
this
this one here.
So, this one. So, this is
our PowerPoint template.
With that PowerShell
file script
that is in there.
With that PowerShell file it will take
this template and
it will add...
This is like an explanation of what I have told you.
Take a look.
I'll go back to here.
So, that PowerShell
will take the results of the review
that you were...the assessment that you were
exploring and will
graph that information here
in this slide.
So, all the information
that is already there will be
put in here.
So, you can have like
a slide back to discuss
and to work with. So,
this four slides.
This four slides.
And with that information we can
define the accesses
to work with and to send this information
to the customer or the novice.
So, it is really
useful because of that. So, it has
the assessment of the foot generator, this PowerShell script.
This is the one that creates
the
file and the .bgbx.
But it also can create one for DevOps.
So, it allows you
based on the information that
we gather in the assessment to create
a DevOps plugin
with all the ethics and tasks
and all that stuff. Also,
with GitHub
and this is
the template for cloud adoption.
The template for DevOps.
The template for what the template
I will show you. So, it's
actually it's my workbook.
So, it's a good tool
to work with and further
explore whenever you want.
So, what we have
done so far regarding the work
is the analyze part.
The first two
ones. You have done all that stuff.
This is where you go to Renegade.
And this Renegade...
This Renegade is where you
actually fix things.
Because there was
this Abraham Lincoln,
one of the US presidents
the founding fathers
had a saying
that it was if you have
one hour to
take down a tree
or
better said, she said if I had to take down
a tree or to chop a tree
I would in one hour
I would take 50 minutes
or 45 minutes to
make sure
my axe is ready
and the last few minutes I would
use that to take down the tree.
Which means that
the success in this kind of stuff is to
dedicate enough time to the planning
and preparation of everything that needs to be done
in Renegade and then after that
start to actual work.
So, well actual operating work.
So, that is like the philosophy here because
the first step is to dedicate a huge amount of time
and then after that is where
you start playing or working
directly with the resources and stuff.
Which is the remediation part.
So, it's like the basic of this stuff.
So, in this remediation part
we obviously have to
back up everything in order to
make certain changes. We need to communicate
what you are going to do. We need to document
what you are going to do. We need to fix
and test what you have done and validate that everything
has been done. So, that is the
reviewing part of that stuff.
So, in general
when you are designing
this kind of solution, the actual solutions
we need to apply the TAP
for the first part of the
process. And the work
when you are already there
and need to be sure that
wherever it is running, it's
following the best practices and is not
to be over the top. So, this work
it's usually
we get a new customer and the first thing that we
need to do is a work. So, you can see
where it is coming, where they are standing.
So, you can work on that.
When you work the TAP, remember that it will allow you
to align business
and technology. So,
because we are on the same page.
And the work will help you to
implement those strategies
into the real life.
Working both
with the strategic guidance
and work with the architectural
practices. We will have
a holistic approach for all the
system or all the
environment.
And finally,
both frameworks
are iterative.
So, what they look for is to
not to apply them once, but
to apply them
at least once or twice per year.
Even once per quarter.
So, because this is a working
framework, it's not always
something that evolves. So, it needs to be
controlled
and it needs to be
aligned with
what is happening in the real life
of the system. So, these are important.
We may be thinking
okay, this is like
boring stuff because it's just talking
and talking and talking. But it has
a really important
and deep level
in the core of what needs to be
taking into account whenever you are
adopting the cloud, whenever you are designing a solution
in the cloud. Because if you have these
fundamentals appropriated
and you apply them to your practice,
you will be a success because
you will be doing what
over 90% of engineers, architects
out there are not doing.
So, you will be over the top, which is
what is this important.
Now, saying that, we are going to
move on into the
next
steps of this process, which actually will be
to take the graph
and the rough
and get into the detail of each one of the
fundamentals. That will be
the governance, the application, the compute
and the storage,
the networking, all that stuff, the security,
the infrastructure, all of that
designing. But everything will be
related to what we have discussed.
So,
before going on, what we are going to do is
to have our
coffee break
for the afternoon. However,
we are going to have it just 10 minutes, so we can
meet here at
4 pm,
yes, 4 pm, your time.
So, we can start with this part
and keep going from there.
So, let's meet in 10, guys,
if you are ready. Once we return, let's check
if there is any questions or any
comments or experience or whatever
Okay, so, let's
continue.
This is the last
of today's session.
So, we are going to do a case study
regarding governance
within
the ASU.
So, in order to do that, we are going to
discuss these items,
general matters of governance, management groups,
financial subscriptions,
resource groups,
the policy center of the government, and the language terms.
The idea
that we could do is that
to have like the
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a                

on 2024-03-04

language: EN

                  WEBVTT
I think that's a good thing.
I think that's a good thing.
I think that's a good thing.
I think that's a good thing.
I think that's a good thing.
I think that's a good thing.
I think that's a good thing.
I think that's a good thing.
I think that's a good thing.
I think that's a good thing.
I think that's a good thing.
I think that's a good thing.
I think that's a good thing.
I think that's a good thing.
Okay, so good morning everyone.
Okay, so good morning everyone.
Okay, so good morning everyone.
Let's start today's session.
Let's start today's session.
So yesterday we were discussing...
So yesterday we were discussing...
So yesterday we were discussing...
Oh, yeah, go on.
Oh, yeah, yeah, thank you.
Oh, yeah, yeah, thank you.
So yesterday...
So yesterday...
Okay.
Okay.
So...
So yesterday we were
So yesterday we were
So yesterday we were
discussing the...
discussing the...
or we were, yeah,
discussing the designing
of our governance solution.
So in this
case study
we had this company
Tailwind Traders
which has two
business lines or units.
one for
apparel and
other for sporting groups.
So this
company had issued
those business units
have three departments
product development,
marketing and sales.
And which
business unit and seat
unit will be responsible
for tracking their
actual spend.
So here is my first question
for you guys.
What does
this line
means regarding subscriptions?
If this line
is in there, how can you...
or let me change or
rephrase the question. How can you
track the actual
spending of
each business unit and
an or each
subunit?
What will you do?
There is a straightforward
solution and there is
an additional solution
which may be a little
bit more complex but it's
valid as well. So
what will you do in order to
solve this specific
highlighted point
that I want to keep thinking?
What about
lean? What do you think
lean? What do you think
it can be done
in order to track
the actual spending
of each one of
those business units and subunits?
What do you think it can
be done?
Perfect, exactly. That is
the more straightforward
solution. So we
can have each one
of the business units to
have a
Azure subscription. So
with that information
or with those subscriptions
we can track effectively
how much they are
spending. So that is one
solution. Which other
solution do you think that
we may have available besides
having
a subscription
per business unit?
I don't know. Who wants
to? Okay, go on Jason.
Yeah, no, I think
that is super valid. Actually, I
was thinking about
another way to do it but yeah,
that works. That one works
for sure.
I don't know if anyone has any
other suggestions that can come
up with. Yeah, for sure.
So we have one solution,
maybe a subscription per each
one business unit. Another
solution may be using
a resource group per
business unit
and per subunit.
So those are
perfectly valid.
And so this is
the goal
of tracking Azure spending.
So which other one
do you think may be
applied?
So we can
think here. For example,
this one, tagging.
You may have tags
so you can
tag all the resource
groups or all the
resources
according to
which department are those
resources in. So it may happen
that you have only one subscription
for the whole company, which
is not ideal but
you can do that. And with
tags, you tag all the
resources which belongs
to a specific department
and that way you can track
all the information of the
spending for each one
of those
departments.
So that is
a good option to do that,
right? So if
you are wondering,
if you are wondering, okay, but how
should I do that?
Let me, let's,
I'm going to access through the
through the desktop.
So we can just
have
if you can take a look
into the training
room. Actually, I don't see anyone
in the training room. So
please, guys,
join the training room
so we can have
a view of your
systems and also
to make it easier
for you to watch
what we can do.
Let me,
in the meantime, while you are
connecting to the
to the
training room, I'm going
to show you here
just, for example, this
resource group,
any resource
group that I put here
and there is the tags. Here are
the tags. So
I can create a tag
for example,
billing
account.
This can be
wherever you want.
Post center
depends on the company.
Post center.
And this is marketing.
For example.
So this is a tag.
So this, that
is how you may want to do
or may be able to do that.
If you tag the
full resource group, well, everything
that is within that
resource group will go
will get tagged with
these post center
issues and so on.
So, so, so
that's it. Okay.
Now,
let's go back here.
So the final
goal of this case study was
to, to, to,
for you guys, was to provide
that company right
Azure Post Reporting Tool.
So the
questions that were
here for this,
for this
study
for this case was
which ways
could you use to organize
the subscriptions and
the management groups? Which
will be the best to meet
these requirements that we will discuss?
And they
proposed two alternative
keys to explain
the decision making.
So I would love
for you guys if you can
share what you worked
yesterday.
The first group
that had some
that used Gemini
as
a discussion partner
or assistant partner
in order to discuss which will be
the best topology. But I
would love if you guys can share
that conversation with Gemini
so all of us can
see it because I think that is
really valuable to leverage
on AI to enhance
our powers,
our capacities. So I don't
remember which group was it.
Sorry about that.
But if you guys, you know who
you are, so any of you
can share
what you did and how
it ended up.
So please go ahead.
I'll stop sharing my screen.
Do you have
sharing permissions or is not
there? Good morning, John.
That is, uh-huh, correct.
No, that is, okay.
That is the, I mean,
to embrace AI, at least
in my opinion.
So if you can share your screen
and show us the conversation,
that would be awesome.
Perfect.
Uh-huh.
Uh-huh. Uh-huh.
That is perfect.
I think that those units have the
departments. Awesome.
Uh-huh. Uh-huh.
Uh-huh.
I agree.
I'm still working. Okay. So let me see
if we can do a really
quick poll here
within the teams meeting.
So let's see.
Let me launch the
Insta poll here.
Let me see if I can. Okay.
Wait a minute.
So, sorry.
Let me delete
this one.
Because...
Okay. So let me
see. Let's vote everyone
with two options.
So which one
would you prefer? Business
unit
focus,
which is the one from the right.
Our focus
unit.
Now let me see
what happens here.
Okay.
This one. So
you can click on the thumbs
up or thumbs down
for the business unit
option. So let
me see how many people prefer the business
unit option. You should have the
thumbs up in your
screen.
In your teams.
So let's see
if you guys have it. Okay. Perfect.
Perfect. There are four responses.
So now let's see
who else
have this one.
Okay. Well, it seems
that this one has
a good number
of votes for at least.
And let's see the other one.
Who...let's see with hearts.
Which one...
Which of you guys prefer the
department focus?
Which is the one from the right.
So in the instant
poll.
Yeah, it makes it.
But it seems that people
prefer the business
unit focus.
And that is...
I mean, there is no
right or
wrong answer in this case.
Because that depends a lot into the business.
But for example, in
this specific situation, if you
take a look, there is...
The business units are apparel
and sports. And those are
like subordinated to the
department in the...
in the department focus.
So it doesn't necessarily
make a business
sense. Because the
one...the business
unit that is providing the
budget, probably
it's apparel from one side
and sports from the other.
So perhaps in this specific
scenario, this is not the
best approach to take.
However, it may happen
in your company or
in a different company that is
different. Because
the product development has
several lines to work
with. So they are the ones with the
budget. So...
sales, housing, marketing.
So it really depends.
It really depends on the company.
So how this works. So, yes,
I do agree that
probably the business unit focus
is the best approach to
manage
the sure key in this situation.
But that
doesn't mean that the other option is wrong.
It's just that it needs to be
applied to the right
or to a more
appropriate scenario here.
The key is who is
the owner of the budget?
Who is the
one who is in charge of the
budget? So that way you can
follow
as they say,
follow the money.
Okay, so
let's see
who other group has...
if there is any other group
who has a different solution and want
to share that solution.
Or if
any other group that has
it can be the same solution because
what I want to do now is
with one of
those solutions
to let place where
the subscription will go.
How the resource, the management
group will be
defined.
So who
wants to share their
tree,
the here key. There was
a group that was already doing that
yesterday, the last
group, the group four I think.
So if
you want to share
that with us please.
Yeah, I
don't...
I think I don't have
the...
Let me see if I can see... Ah, no, I have the
list here. I forgot.
It can be Kevin or Kempi
or Pierce.
Any of you guys?
With you?
Awesome, thank you.
I have the list here. I forgot.
Oh man, you are the greatest.
So, okay, so he already
has the group
four with Kevin, Kempi and Pierce.
Already have the
the
management or the
the root groups.
So these
the management groups. So
go ahead and explain that to us so we
can discuss. But this is
actually what I was
wanted to do.
I can see the governance.
R2 governance.
I can see, let me see.
So here in the
documentation, so we can
create a management group
in all services,
management and governance.
Why I didn't see it? Ah.
Here, let's see.
Microsoft
all services.
And then
here. So
all services, management and governance.
So here are the
all the different
options for the
management and governance.
But I'm looking at
ah, final.
I wasn't able to see. So
these are the management groups. So
by default, there is
one management group.
So there is
one management group, which is
the root group, the
tenant root group. Yeah.
But
and in this
environment that we have here,
we don't, we have like
a proper
design and
tenant. So perhaps
in this example from
other training.
So in these all services
management groups, you can have
that is
hierarchy
that we just created. So you can
create the tenant root group,
which will be like
the basics of the company.
The organization
example. I'm going
just to create a
example here.
Organization example.
So here
this is the organization
example.
Art link.
If we want to do
the example, we can
create the
So this can be like
management group.
And then I
send the sample.
So, okay. So
create here.
Okay.
It might take a
while.
Okay.
So, so
always use the tenant root group. And
under that is where you create
your management
group or your organization.
You can add this description here.
Or you can create the structure.
So there was the
apparel.
Apparel.
And there was
the
spots.
Spots.
Yeah.
So let's create a little
bit like this
apparel.
Spots. And
here so I can create
the marketing
one.
Marketing.
And sales was the other one.
And it was written
apparel marketing.
And sales.
Sales.
So that is what we are doing here.
So with this
organization or unit or
with this management group, what
you should do
what you should do
is, okay. I'm trying to
copy what the
group one designed.
So here I
will add the subscription.
So
I'm not going to do it.
But I will just
have one of those subscriptions.
And move those subscriptions to
this management group.
Right.
And I
can even create a new subscription.
Okay. Yeah.
So here is where I create the subscription
or assign the subscription to
this management group.
And with this
unit or within this unit is
how I can give access
to the
different
actually
I'm going to keep using this
this
this desktop so
we can
we don't have to change the screen
as well. So that way
is how I do it.
And this kind of stuff.
So let me erase it.
Clear it here.
And all
the policies and all the stuff
goes in the
so
yeah.
Okay. So that is
what we were
supposed to create.
So in this
case this will be
the management groups. This will be the
subscriptions. This will be the resource
group. This will be the policies.
The
and the tax.
So these are like the objects that
we use in order to
achieve that
goal that we have in the
case study. The next
lab, the lab 16
was related to
to this
tagging and policy
stuff. So
in this case what
we want to do here
is to okay so
how are we going to
ensure that the
costs related with the project
in particular are
captured
and the virtual machines which
naming should be used
or how
rules are we going to use in order
to have this
manageable.
Like being able to manage
to track the costs for any
new project, to
issue compliance of sizing and
menus.
And how are you going
to discuss this. Please
So basically
here what we are referring
to is to this
naming convention.
So this is
the name convention.
So this is the
name convention.
So this is the
name convention.
So this is the
name convention.
So this is the name convention.
So this is the name convention.
So this is the name convention.
Either using this
template
that helps
you to define a policy
for your applications,
projects, business
needs, cost centers,
projects, everything.
To for tagging,
for tags.
And your naming, how
are you supposed to name
the sources.
So the objectives of
that second part of
the lab are to be
and here is where
like the predefined
names
that are created.
So this is, this would be like
this template
should be at least
one of the
deliverables of
the design
with a proper
adoption of the
framework that we are
working on. And the
other components here
that is really valuable is
this, the tool, the Ash
remaining tool that
allows you to make
this to
work, oops, it has
to generate
these names.
So with this tool, remember
that you can like
set up how
this is going to work
if I do have units
or not, if I'm going to
use projects and services
and functions. So do you define
how do you want
to create the structure
of your
name and
your environment and everything. So
these, these,
I really recommend you guys to
take the time to
play with this and see what you
can produce because
I mean the amount of options is
really big.
In the example from yesterday
it was a name
that we generated for
Linux and we used
like everything that was
available here but perhaps
it's not really necessary
for the use case or
for the company. So
this is something that needs to
learn really business with technology
and see what
the needs of cost accounting
and all that stuff. How are we
going to work with that?
This is what you need to take a look
into this. Okay.
Let me know if you have any question
in the slide number
208. You will
find the links to the
different documentation
related to this
factor so you
can get a little bit more
in depth with
the options
as well.
Really quick,
this other
lab will help you
to list all the
role based access control
available for
the resource group so you can see
what is in there.
So it is
so here
you can see
the specific resource group
resource group
here.
And you can
see
the
access controls that are available.
So you have access
or if you want to check access to
other resources. So
this is that
just to clarify a little
bit, this training is
not supposed to see
how to operate, how to do
this kind of stuff, but to
understand what the rationale
behind this.
So then once this is
designed, you can operate
or implement this kind of
stuff. So
just for you to have the idea.
The same with the policies.
The policies are here.
What we will
define the policies
here is
a policy sheet.
Or you, the policies that are in here.
Because most of them are
already there. Remember
what I showed you.
That there were some blueprints
that did you
apply those blueprints.
You
do a cloud
configuration.
It will be ready to be
certified for ISO
27000, for example.
The Hapgram
level one.
Certifications.
It's all here.
What you see here is that
that list of certifications.
So, obviously
the best
option of practice is to
start in the very
very basic. Otherwise, you
may have a lot of
issues. Because
you are not allowed to do certain
stuff that you need
to do. And because of the policy
you need to
change the definition of such
blueprints. So it's important just to
take it slow as well.
And, okay.
So, let's
go. Let's move on
to this.
Okay. So, now
what we're going to discuss
is the
designing of
app service or web app.
So, in order to
do that, we do have
this
decision tree, which is
super useful.
And this is something that
at the end you
want to have like
not memorized,
but just
you need to have
as clear as
possible
in your mind.
Because this
decision tree
allows you to choose
which kind of resource
you need to
use to
for your work
load, to move your work
load from on premises into
the cloud. So, which
will be like the best solution.
And remember
that we discussed that
when you are moving into the cloud,
when you are loading up into the cloud,
perhaps from the five
hours from GARNET,
the mass common one is
just to use the virtual machines,
lift and shift, and go there.
But that way is like this
challenging hosting for vagrants
and you are losing all the
benefits of having the cloud.
So, this
decision tree helps you to
realize the value of
moving into the cloud. So,
here let's do the process.
So, this is page
211 for the ones
that are following the
slides. So,
the start. So, if you
are going to migrate,
remember, migrate or innovate.
Right? So,
in this case, migrate or build
a new instance.
So, if you want
full control, and this refers
to the operating system
plus the applications
and the middle
world that you
put into this virtual machine.
So, this is
a way to do it for that.
If you don't do it for that,
go ahead, Kempi.
Do you have any questions?
If you
don't require
full control,
so it doesn't matter
if it's Windows or Linux
or whatever.
So, it gives you a different set
of questions. For example,
if it's a high-performance
computing workload,
if it's a
microservice architecture,
if it's event-driven
workload,
if it requires
full orchestration,
if it requires
integration with
.NET
or a stack
on Windows.
So, all of these options
will provide you
a specific
resource or service.
So, you can run
your application
in the most
optimal way.
So, if you invest
in the case, it will be
a new application. Go on.
Go ahead.
Okay.
So, when you're integrating,
the questions
are already there, but the outcome
is kind of the same.
So, are you going to integrate?
So,
are you going to lift
and shift, so like
properly the virtual machine
and make it run
on the cloud,
or are you going to
optimize for the cloud?
So, if you're going to optimize
the cloud,
apply the same set of questions
applied.
Is it high performance?
Is it not a service? Is it self-enthusiastic?
Is it requires orchestration?
Is it
.NET integration?
Or is it not
the Kubernetes service?
If you're just going to
lift and shift, the first question
will be, can this be contained?
So, come to my eyes.
It turns out
that it is surprising
how many monolithic
applications can be
containerized. I mean,
PHP application, Java
application,
but net applications
can be
containerized. So,
that is,
those applications can have
a lot of container. So,
it's something that is
that hard to achieve with a lot
of applications. So,
this is something that is
worthy to analyze
and see if it's possible or not.
So, if it
can be done, the question
will be, do you need
full orchestration?
If not, go here.
If you
do need orchestration, you
have two options.
Use the Kubernetes service or use
the app service.
So, it depends on what you
want here.
So, if the application
cannot be
containerized,
you can see the
app service, depending
if the language is
one supported
by this
service, or
if not, the virtual machine.
So,
the
point here
is that
this is
counterintuitive.
It means that the only
way in which
you may end up
with a virtual machine
are kind of the
extreme cases. So, there
are two options for
virtual machines. But,
after discarding,
everything else, almost.
Right? But,
in the practice in real life,
this usually is
the first option. So, it's the
most common option. But, it
doesn't really need to be like
that. I mean,
a lot of applications
can be run as
app services. And, a lot
of applications can be
run as containers, either
in Kubernetes or
in some containerized
instances. But, this service
was appreciated.
The release and search
changes in this service are
more in the Kubernetes one
and in the App Service one.
But, the point is that
virtual machine is
not like the first
option, but
in the
decision tree. But,
in real life, it is
probably popular
as well.
So, with that
discussion in planes,
let me go. Let's go.
Let's see a few
more steps before going
to our next
study. So,
here there is
another decision tree
to help you
choose when to
use an app service.
So, the app service
is mostly web applications,
but it can also
be used for, for example,
mobile backends or
REST APIs
or jobs that you
want from time to time.
It supports different languages.
This can
scale. This can be
connected to
your CI-CD pipeline,
either a GitHub
actions or edge drops,
whatever. So, you can use this
to deploy from there.
There are some considerations
that you need to take into account.
The most important
one is which is the plan
that you are going to use,
because that is the cost, that
is what defines the cost
and the
scaling capabilities.
For example, this
is
the report sheet.
So, this is
a resource group with
app services.
And here we
have what is called the app service
plan. So, this app
service plan is
basically
you can call it like kind of the subscription
of your
web applications.
So, this
app service plan,
and let's see where it's
in.
Okay.
This service plan is
in the free time.
So, it doesn't cost
at all.
It gives you personal instances
and what in this case it only
has one instance, but it can be
more instances
if you require them.
So, this is an
instance of that plan.
So, an instance is
basically an application
that can be run
in a specific
container.
So,
let's give it a minute
for this to load.
So, this app service plan is like the
hosting plan
or the
former hosting plan that we have
in the distribution data center.
So, okay, let's wait
for it to load.
So,
in this app service
you have like all
the options that can
be configured, not
the deployment.
So, this is linked
to CI-CD,
to App Island. The configuration
so you have
back-ups,
domains, certificates,
you can scale up or
scale out your system.
Well,
it was started and going to stop it.
So, it has
a domain name here.
It is a PHP application.
This has the IP address.
It's a
Linux server.
If you want to scale this app
so you can
have like more power
of the system.
So, this is, I mean,
this is instead of
having a
server with
Apache server, with
a PHP page,
you just deploy
this app in
Google AdWords. So, this is the
features of this
kind of
workloads.
So, the ones for development
and testing
that, for example, the free one
gives you
a maximum of 16 minutes
per day for free
of service of this application,
which means that it can only
be like one hour
use during the day
for a maximum of one hour.
And the
productions ones, which
are the ACU, which
is like the capacity per unit.
So, they have the data.
So, this is for
production workloads, but you
can see that we are taking
about one virtual CPU
or four virtual
CPU.
In this extreme case,
32 gigabytes,
250 gigs.
The SOA that you have
available here. And the
cost of these things is
super cheap. Per month,
per month, 73,
$1,600,
up to $300.
So, the thing is that this
can have a lot of
websites or
backend services
available around
this environment.
So, this or that is
perhaps one of the most important
things that you need to
define when you are choosing
your web service app
as well.
This is an
example of an architecture
using
one of these.
So, you have the
directory, the DNS,
for resolution. And you have
the app service plan with the
web app and different
environments.
Production, scaling,
which is the first one.
And the last good production
or last good operated
environment.
Database backend.
So, your application connects to this
backend.
And this is monitoring.
So, if you have
monitoring enabled,
if you pay
close attention
to what I was
telling you, you will have
noticed that this doesn't have
application enabled
in this machine.
Because
obviously that costs. And this is
just like a demo stuff.
So, there is
no need to
have it that way.
So, that is
like the web application.
We have a few
labs here to deploy
web application
using this guide, the
.NET 4 guide. But
there is this
other one that
is also super nice.
Because there are
this one allows you
to deploy a
.NET web application.
Either from this
to the code or directly
from the portal.
I don't know why it is
loading there.
So, it's just like a sample
application to deploy.
Or there is
this other
lab
that deploys a
very
more
big
or a bigger
application here.
In DevOps
with DevOps demo
guide. So,
let's give it a try.
Let's have like
a few minutes
here. So,
we choose
App and Play. There are
some applications
here. I have suggested
any of these. My shuttle
help, cleaning parts,
unlimited, smart portal.
So, what we are going to do is
let's go to the
again to the
our
our breakout rooms.
And as we have
multiple applications, what we are going
to do is that the group
number one will deploy
my shuttle. The group
number two will deploy my
health cleaning. The group number
three will deploy parts
unlimited. And the last group
will deploy smart portal.
It may happen that
the application doesn't deploy
because there was a change
or something like that. I mean, this
this cancels
up. So, it may happen
that it doesn't, it fails
or something. But do not worry
about that because what we want to
see is like what this creates,
what this generates. So, we can
have a better understanding.
So, I'm going to
send you guys to the groups.
Although there is something
up here. I mean, yesterday
I see that Alexander
was
working with Charmaine.
And Charmaine is going to,
I mean, she's a rock star because
she has attended like
more courses, trainings
that you can imagine.
So, let me
I'm going, Alexander, I'm going
to move you to a different group so you don't
be alone.
No? Is it good?
Okay, cool. No worries.
So, let's open the groups
and go from there.
This is page 217.
We can work like for
10 minutes.
And then we will get back here
as well. So,
yeah, go on.
Yeah, as
soon as you get in the room,
we will show you this room number.
Okay, so, let me see.
I think there we have
the whole discipline here.
Okay, now
we will do so.
Hello, guys. How are you doing? I was
having issues with my
with my teams.
But now I'm back. So,
how are you doing? Are you
deploying already something
or which one are you?
Awesome. Okay.
Cool, cool, cool. And take a look
with this. This is
the board that you also
can take a look into the repos
and pipelines.
And actually in the
that is the application.
And
take a look into the pipeline.
So, this has the
the proper application
created. So, you can
run it, run the
the
pipeline.
Choose
the
for example, the
choose that one.
And run pipeline.
This pipeline creates
a, or should create
a Docker image.
A Docker image for the
application.
So,
and then go to releases as well.
And the left
column.
And you should see here
the release of a
container.
So,
as this project is fully
set up, everything
is in place. From the board
to the backlog and
everything, to the source
code, to the pipelines
that, the CI
that creates the images
from the binaries. And the
CD pipeline that
deploys the application into the
web. So, this is
super beautiful because it has the whole
package. Yeah, the, all the
idea that you hear about
okay, let's do devops,
let's do automation,
let's do moving to cloud
blah blah blah. So,
that is in here. So,
the pipeline, the first one
that you'll watch, go back there.
See if you've already finished it.
It may take a while.
It's
it's still running.
Ah, it got cancelled.
Let me see.
It may fail because perhaps
it's too old to be honest.
Yeah,
it wasn't able to. I mean, it's
requesting for a, to be into
16.04 and that doesn't exist
anymore. But that pipeline
creates
the binary. And that
which in this case will be an image,
a vector image. And the
release, the release
will take that
image and deploy that
into, in this case
on app service. So,
take on create release, it will fail
as well because it doesn't have an image
that's
to
the
to
Okay, it's using the
my shooting
if you want
to go to pipelines and
let's see the other one.
There was
an all
the, try to run
that one.
Okay, no, there is no pipeline
there. Let's see
that.
Let's see, so these
these
projects
maybe out-added
they
have a lot of stuff
open up to you.
Let's try with another
with another of the pipelines
that are in there. My shooting
try with the Docker and then I shuttle
build to see
if it works. Okay, this is
more recent.
We can try that
the, try to run
to see if it runs.
And perhaps
you can change the Ubuntu
18 to almost recent
one.
And see, yeah
try, try to
Ubuntu
later, later something
on run.
And this can
this project can be
adjusted so they work.
But it will take us
too much time. It's just
to have an idea.
To see if it works.
Okay, let's
give it a try. Explore that
what was done in there. And if
you want to, you can take a look
into the other
deployment of a
web app to see how it works.
It seems it's running. Click on
phase one and you can see the
load.
Okay, it seems
it's running. So as soon as this
finishes, go
to releases and find
the corresponding one.
Okay, it plays the maiden.
Click on the
maiden.
This is the life of a DevOps
engineer. I mean, what you're seeing
here is what our DevOps engineer
does all the time. Because
the pipeline is failing. So
what you will have to do as a DevOps
engineer is to
let's see why it's
playing. It was because, I don't know,
the version
of the library or
wherever. So we need to adjust
and do whatever.
Or there
is a need of variable
that is not set or something
like that. So
that is like what you do
as a DevOps engineer.
Try to use a different image.
The 2004.
Perhaps because
I mean, probably as this project
is old,
the versions of the libraries
in the new one doesn't work
as expected.
You can give it a try.
And you can also try to deploy the other
that net application as an app
service to see how it works as well.
Okay?
So see you in a while.
I'm going to the other room.
Okay, guys.
How are you doing? Let me show the
error, the message. It
seems that it's asking you for
for
Okay, it's asking for the
name of
the project. Ah, the organization.
Which organization are you using?
Okay, that's the application.
So you need to give a name
for that application. So
name that
and dash your name so it can
be unique.
Perfect. Group
two. You are two.
Uh-huh. Uh-huh.
And no,
no, you cannot use spaces.
And uh-huh. Perfect.
So
it may fail to compile
because these
projects are kind of old.
So it not necessarily
will compile completely.
But you can see the full
structure of how
the DevOps
is implemented and all
the components and
hopefully the web
application will be
will be deployed at the end.
So, so you
explore. Let me, I'm
going to be back here in a while.
Let me go to the other groups to see how they are doing.
That will be nice.
Hello guys. How are you doing?
Oh, very
good.
We're able to deploy.
Congratulations. Yeah, because
I was telling you
awesome, awesome.
That is great news. Because
the thing is that these
projects
may be kind of old.
And not necessarily
will be deployed or will have
failures while compiling. But
in the case it seems to work.
So super cool. Nice.
So I'm going to
use you as
the demo later.
Okay, keep going there.
So see you in a while.
Hello
guys. How are you doing?
Okay, it's creating.
You are creating them. I hope.
Okay, cool.
Let's see how it goes.
So not necessarily
complete because
these projects are kind of old.
So perhaps
it doesn't deploy
or, well,
is able to deploy the full application.
But you just can see
all the components
that are in there.
Let me see the pipelines.
Which one is this?
Let me see the pipelines.
Okay, there are no pipelines.
And releases.
Okay, very sorry.
Let's try to launch a release.
Yeah, create a release.
Why is it showing like that?
Click on the plans.
When you click on the
My Health Clinic E2E
in the middle
column where it shows.
In the middle
column it says My Health Clinic E2E.
It doesn't show anything.
Here, here, here. Where we are?
Here.
Right button.
What does it show? The right button.
The right button.
The right button there.
It doesn't show
like the menu, no.
Click on the blue
button that says Create Release.
And see if it works.
The blue button
on the
tab.
Yeah, it shows that.
Yeah.
It's not showing you
any of the
we are testing.
Okay, the artifacts
deployed there.
Okay, there
are no, okay, yeah, because
what I see is that the pipeline
is not there. Go back to
pipelines. Okay, it wasn't created.
And is
the demo generator already
finished?
Okay, okay,
okay, okay.
We can see
ah, exactly.
The pipeline is what it was
failed.
Oh, that is
true.
Let's
okay, let's see.
The thing is that not all of
these demos work.
But
one of the things we're able to
play the demo.
So we are going to see. Give it a try
to see if it works. And I'm going
back in a few seconds.
Or I'll call you back to the name in a moment.
So we can check. Okay.
Okay, guys.
So, well, some of the
some of the projects didn't
deploy. However,
the
team from Alexander and
Blair, they were
they advanced
a lot. So, I mean, it
was able to deploy the web absolutely.
So if you can share your screen so
we can take a look, all of us.
And also I'll show you
mine to see.
Yeah,
please do.
Yes.
Yeah, well,
kind of. Let's see
if it works.
Okay, okay. Yeah.
Okay.
Okay.
So let's let's go to the
DevOps so we can see the
project. Oh, no.
This is the portal. So go to the
DevOps, which is the next
tab that
you have. No.
Okay. So
let's just. Okay.
Okay. Oh, yeah. Okay.
Let's see the work spirit.
So this demo generator that
this creates is a full project
with the backlog
and the five, the red posts from
the source code and the pipelines
and all that stuff. So this
is just an example, but it gives you
like a general idea of
the whole process as well. So
okay, this is the backlog.
Let us show us
the red posts or the source code
piece.
So this is the
report for the application. In this case
this is an ASP net application, a web net application.
And something interesting
here is that file
that says Azure
pipelines, but it has a lot
of branches.
No.
Before going there, look
in the middle column. There is
a file that says Azure dash
pipelines 1.0.
In the middle column.
In the column of the middle.
Uh-huh. At the end.
In the middle.
In the column of the middle. The middle column.
The last
the last, no,
the other
to the other side.
In the middle there are three panels.
So the panel in the middle.
And the one
No, that is the third panel
from the second one.
And
that one. And the last one.
And the same
on the other panel.
Uh-huh.
Last file, last file.
The other one.
So this file
is the general file of the
pipeline. So this is
like the instruction set to deploy
this application. So here we go.
Please go down.
Down, down, down.
A little bit more down.
Here I think.
Line 81.
So the
line 81 is the
deployment task of the
Azure app service.
So this deployment task
what this creates is
the app service that we were
discussing a few months ago.
So the subscription,
the name of the web app,
where it's going to be deployed,
the resource group, the
app consider is going to be deployed.
So that is
those about ten lines
are the key of
the deployment into the web app.
Before that is all that
process, no? So
the scope of what we are
doing here. So this is having
in mind how big, how huge
this is. Because
the only scope
of what we are discussing is
which are the
trade-offs, which are the
design decisions
in order to decide
what to put in those
ten lines.
So all this
discussion of
the CAF and the WAF and
app service and what comes next
is just to decide
what to put into those ten
lines. So this is
huge. Yeah, so this is
huge. I mean this is a file with
I don't know, 100 something lines,
200 something lines.
And we are discussing those
that we wrote. Okay? So
because before that
is the developers
part and the
infrastructure guys and all that stuff.
Now, you can go to
the blue rocket in the first
panel, the filings.
No, that one.
Okay. This filings
is, click on there please.
This is the
the pipeline that
that we just saw.
We can run it here.
Don't do it
because as the deployment
runs itself, we may
break that. It's already broken
but I want to show you
what it is. So when we run
this pipeline, what we are doing
is executing that Jamf file.
And this
will create the app service
and deploy the application into the app
service. The application
is just a zip file.
For example, imagine
a PHP application, which
perhaps is simpler. So
the PHP at the end,
it's a folder
with a series of PHP files
and a configuration
that points towards
a device. So that
is going or that goes into
a zip file and that zip file
gets unzipped
into this container
or these app services
and that is how it
serves to the public. This is
the general idea.
So that is what this does.
And go to releases, just
in it, pipelines for
UR, in the same
rocket, uh-huh,
releases. No, no.
Ah, that one.
So these releases is
when the pipeline creates
the zip file or the binary
or the image, this
is sent to the app service.
So the release part is
what the one
in charge of that. Probably
in the test
plans, in the purple
icon,
there are
some test plans.
Yeah, okay, this is a
test plan. So it checks
the application. For example,
here you can check the application
it has
errors
in the code, and stuff like
that. And
you can automate that. And
the artifacts, and the artifacts
in the
in the
icon, the test
plan, artifacts, artifacts
in the, uh-huh,
probably you will see the
zip file for this
plan. Yeah, okay.
Okay,
it will show anything.
Well, it should be there
somewhere.
I have to see another one. But no worries.
Don't
waste too much time here.
Let's go now to the portal,
to the portal, to the top
of the actual portal.
No, the portal.
Uh-huh, uh-huh.
So here, can you
go to Chrome, please?
So,
resource groups, can you type
resource groups?
Uh-huh.
And you should have a resource group
for this application
that you created,
which is, okay, that is the name.
So here
is where we have the
project. So we have
the plan, which is the
hosting plan, and which
it defines how are we going
to handle
the loads. So can you
click there in the plan,
please? No, in the
middle, in the
middle, in the last panel
where it says app service plan.
In the two objects, in the
two objects, uh-huh, down there,
down there, no. In the two
objects, which in the middle,
the biggest, the big panel,
uh-huh, the big panel, uh-huh, uh-huh.
And, okay, those, so the
second one, the app service plan.
Go back one time
to the network
and the plan where it says
uh-huh, that is the plan.
So this is the plan where
you can have multiple deployments
here. You can say that
this plan is like the matching where
your application is going to run
in the general way. So this shows you that.
And in the
in the left column,
you will see apps,
the icon apps.
So here are the apps that are
running into your plan,
into your machine.
So now you can click there.
And this is the actual
deployment that was made.
So it shows you
the URL.
This is our Windows machine.
This is the runtime
stack.net.
The
wherever, so all the information
is at the center, the
line, wherever.
So if you go
to the default
domain and open that,
which is the page that we
showed you, show us
at the beginning.
Oh, no, in that page
it says default domain.
There, there.
Open that in
the top.
So that is the application
and it is
not loading.
But I think that you have
one, show us
the one that
open, yeah,
is the same. So here it's failing
and it shows that the error
is because it says that it's not
finding the web
config file, I think.
But
it doesn't matter
right now, it's like
the ID. So what we wanted to see
here is an
example of how to,
of how to, well, in this case,
to see all the
DevOps process,
which is outside of the scope,
but it's good to
have it in mind so we can
know where we are
standing up and
see finally that
web app service that we
were talking about
as well.
Okay.
I tried to deploy
the smart
hotel application
that we failed as
well. Let me see.
Let me see if
it was able to create
any results here
or if not
an access to
the system.
Yeah, so I
don't know if any of you guys
were able to launch
your application
or if any of you
launched the
the
AppSorti directly
to the other lab.
Any of you did that?
It's okay if you don't.
It's not
easy at all.
Okay, so maybe
maybe so now is
fine. Okay.
So that is
what the app service
is about.
I'm going to go back into
this.
Okay.
So, so, so
these two components,
well, this
box, this component is
the one that we were
talking about. The app service plan,
the app service web app.
These two slots
are the ones from
the pipelines from the
DevOps environments.
So you can have
multiple deployments
depending on the
environment or the
stage of development
of the application.
So this is this
component of
the whole solution as well.
And the
criteria that is needed
here in order to work with
these kind of applications,
this one, what kind of service,
if you're going to use some
kind of deployment, if you're going to
have apps, mobile apps
using
these
web apps as a backend,
you can have authentication,
you can have REST
APIs here, you can
use these to run jobs.
So this is like
a really flexible way and is
not that expensive compared
to having a
what?
A full
built-in machine running that
because in this case
you have
well,
if you take notice,
almost all of
these were Linux, but the parts
were limited with
a Windows application.
So at the end, you
go online because
the service is able
to understand based
on the code which
kind of image
needs to be assigned
in order to deploy
this application on
a native web.
Okay,
so we're going to do
a small coffee break
and we are going back in
order to discuss all the
storage items and the
designing decision
of storage solutions
for Azure.
So we will discuss
the storage
towns, the redundancy, the block storage,
the files, the distribution,
the security, and we will
have another case study.
This case study
is
this one.
This case study
is for the same company,
but we are working out
which kind of storage
solution are we going
to create or to
assign for them, provided
that they have, for example,
media files
with photos and videos,
marketing
territory, which are mostly
PDF files,
with suppliers and stuff,
and corporate documents, which
are VC-Sephatch,
have documents
with sensitive information
in common office formats
as well.
So that is
the next case study
that we are going to work with.
But first, or before that,
we are going to like to discuss
all these components,
so we have an idea
and we'll do that.
So let me know,
if you have any questions.
If you are good to go,
let's have
15 minutes.
So we can
ask
that will be
11am
in time.
Okay?
Okay.
So let's see
guys.
Discussing the
storage components
and let me know
if you have doubts
or whatever
you have seen
previously.
I've discussed it
previously. Otherwise,
let's just
discuss regarding
these storage components
or services available
within Ashwood.
So first,
we need to
have a meeting time.
But there are two kinds
of data
storage.
One is, or top data.
The first one is
the non-relational data
which refers to
files,
either media
files or
documents or
PDF files.
And the second one is
the non-relational data
which is non-relational
and relational data
which is basically
SPL
format
or scripted
data.
So this
is regarding the
assignment of those
storage solutions for
non-relational data.
This is where the non-SQL
services
like Topology
go into action.
So here,
the first one
of the
components is the
Ashwood storage
accounts.
These storage accounts
are the
basics
of how to handle
non-scripted data.
These storage accounts
allow you to
have or to define
a series of
pictures
that are related of
the way you handle the data.
These features are
related on, for example,
where do you want to locate
your data and which
criteria are you going to
use to
locate some of the data.
You are going to replicate
the data in order to have
a
redundancy.
You are going to provide
these other options for
storage so that
is something related to location.
Regarding compliance,
if you are going to
have storage
with sensitive
data or storage,
we mentioned that
because of some legal
requirements
needs to be stored
for five years or
ten years, so it's similar to that.
So in that case,
we will use limitable storage
so that doesn't change.
Another criteria is the costs.
If you want to have
hard access,
so it's storage of
files that are currently being used
or it's just
archive storage that is
stored for
inventory use
that or
code archive
that is not
frequently accessed
for information.
Also,
if you want to have
different kinds of verification,
either local redundancy or
location redundancy
or
we have access
redundancy, so there is
different verification
requirements.
Regarding the administrative
overhead, how are you going
to find this data?
If there is
after a certain
while the data in this
container condition
in this account is going to be moved
or called archive
or is going to be
erased, it needs to be
indexed, it needs to be
available for both searching
and etc.
So how is going to be
handled that?
How sensitive is the data?
So if you want to have versioning,
if you want to have exact
search, if you want
to have
font-inflated restoration
and so on,
also
the handling
of the authentication and authorization.
If you are going to
leverage an active directory
or if you are going to use
a key,
a SAS key, a signal tool,
to access the data.
Which kind of service level
are you in?
Are you going to have 99% or 99%?
99%
If you are going to have
which kind of account
are you going to have?
If you want to have a system in general
or a premium account
for the roles that you have
in the future,
etc.
These are different options that are
required
and that are needed in order to
design or define
which kind of storage are you going to use.
First of all,
deciding
on which type
of storage account
are you going to have.
The same
choice with
the standard email,
which is 1.4,
this is standard email
for the required services.
This is important
to ensure.
You have the account type
and you have services
that are
related or are
classified in this account type.
So, depending on
the level that is
available right now.
This one can be used in
almost every other
scenario that is available.
There is a
premium ones.
You have the block under the legs,
the files and the face blocks.
So, those
are for specific
use cases.
The premium block
is for small transactions
or high transaction rates.
So, it's something that needs to be
stored with a high
amount of transaction
rate.
We actually
find things that are
stored in
files
and traditional
resources,
charred resources in the network.
Or the
face blocks
which are required for example.
So, you need to provide
a low latency
storage and high
performance storage
for your application in particular.
What else do you need to
have in mind? The location.
The closest
to your customer,
the data or your clients,
your users.
Which regulator,
which guidelines
or the regulation needs to be
fulfilled and the costs
of these services.
Obviously, the premium services
are more expensive
than the other ones.
If you are going to have reputation,
you are going to have different
requirements
for these
both sensitive and
management activities.
So, one of the most
important items to have
in mind is redundancy.
So, the ability to replicate
people's storage.
So, you can have
within a regional
cluster redundant
storage locally to the region
or redundant
among different zones
within the same region.
So, this means multiple data centers
but in the same region.
Or you can have
additional, you can have
a secondary region, which means
that you can have
a copy
or replica of the storage
in a complete
different region
in the world
for the data.
So, you can have
an example in India
in the India region
the main data
and in Australia
a replica of that data.
So, you can have access to both
in case of a failure
a catastrophic failure
in the India region.
So, that is
the availability.
So, this is like
an example of how this
can be seen. So,
in the replication of the storage
you have the data center
with the storage account
in the primary region
this will be locally
redundant storage
so multiple copies in the same
data center. When it's
zone redundant
you have multiple data centers
different data centers
with multiple copies of the data center
that this is in the same region.
So, this is India
and this is India as well
but three different data centers.
So, I mean
if you think
or if you map that
to the own premises
scenario, the traditional
scenario, that is something
that is almost
impossible to achieve
without
a lot or a huge investment
for a
common company, a normal company.
So, you have three data centers
in different countries
that is not something
easily done.
So, that is why
this is so important. But
the answer is tricky.
In the sense that
this here
doing that is super simple, super easy.
But it has
a cost. So, okay.
Do I really need
to have a replica
in another continent?
Is that really needed
for my requirements?
Or just having the
copy in multiple data centers
is enough? Okay.
But what happens if you lose
access to the
internet connectivity
to that country?
Okay. So, you need to take
into account the price
of the requirements.
In this example, this is the
the remote
geographical replication. So,
this is one region.
This is a different region.
And here is like
the same situation but with some
replication
as well. So, in different regions
and secondary region. So,
this is like the highest
option available
regarding that.
Okay. So, those
regarding location. Now, regarding
the type of storage.
So, you can start up the storage
that is available
in object storage.
That is available
using an API.
So, the
blog storage will be
like the object storage.
The three-order tree testing, which is
right there most. And common one,
the one that you choose most.
But there is also other
other thing, the cable storage, which
is kind of
SQL.
Not necessarily
SQL, but it's just like a table,
a matrix, where the storage
is the same
for other three-order
research. And key
storage is in a
segment with publishing,
subscription mechanisms to
access the data that you
have to pick. So, these
are programmatically
accessed. So, this is
requires a client
to use an API to access
the data.
And this other one
is
like the more
traditional way to access
the data,
which will be the file
storage, like SMD
or SIPs. And the bit
storage, which is
hard to search.
So, here
is where the blog storage
shows up. So, the blog storage
the criteria for
designing for this blog storage
is the file. So,
if it's spinning, which
is the
performance,
it needs the standard
but packed in the sense
that it is used
differently or
if it's full or
if it's hard type, when
it's used by backup,
short-term backup or long-term
backup. So, these are like
different files
and the ones that we use
usually are the premier
and the second half, depending
of your use case
and requirement.
Also, you can have
policies here to enable
storage. So, these
can be only read
but not written.
So, you need to
store documents
and put a
layout requirement or
policy requirement. So,
you can just write
once and read
multiple times.
So, here are two examples
on how to use
the blog storage. So, you have
a briefing screen
and how to have a chat available
in a blog storage of
these descriptions. So, this will be like
any sort in there
or in this case,
this will be kind of the same
but using a telephone
app or
the things like same kind of
screen. How to use
the fire. So,
basically, having more load,
performance,
requirement into those
requirements, those two
and the rest can go to
depending on the
what is needed, the product of all
or this kind of.
Now, for actual files,
that is all that is needed.
Actual files,
here is the discussion. So,
when you should use actual
files versus
blog storage. So,
depending on
the kind of
input output that
you are requiring,
depending on the
file sharing scenarios
that you are thinking about,
is when you use
actual files. So, actual
files is the one that
gives you access to
features like performance.
So,
300 megabits per
second or up to
5 gigabits per second
of performance and access in
this file.
Handling of identity.
So, this file is still
the way to access this
either like a standard
share into the system,
the root machine or
by synchronization
of the files like the service
running and synchronizing the file
with different redundancies
and different tires,
exactly the same as the one that we
discussed earlier.
So, they use cases
for actual files
versus actual
blog storage. So, when
you are replacing the files,
so this is like the most traditional
one because here we are talking
about non-constructible data.
So, this is what we have here.
And it's successful
by traditional means,
usually SMB or
NFS or
WebDrop and it has
a little bit of
performance.
And the blog is more like
OK, backups,
media
that is like a
content-dependent network
or analytical data.
So, it can be used with
NFS, VLS
or with database.
So, this is not like a focus,
but it's more like an application or
systems data.
The structure of these
types of files, so
you always have your storage account,
the service as you find
and the shared resources
with
the corresponding
directories of those shared
resources and
specific files that are
available.
Regarding performance,
so you have
the latency
and depending on the
type, if it's standard opening
but you have to
take into consideration
that this mostly
depends on your
internet connectivity
or how are you
connected to the actual
cloud. So, no
matter if you're using standard
or premium, if your internet
connectivity is not up
to the task, you won't
notice the difference because it will
only be as low.
So, this is something that
the limitation is not properly
in the cloud, but in your
last-money access.
This is
an architecture
describing how to
have, for example,
a file synchronization
agent with
On-Premises Data Center and
Azure Cloud
Services.
So, the file here is
accessed by
virtual desks in the cloud
or servers, but
from On-Premises, the information
is accessed using
file synchronization services.
So, this is like
one of the options
that are available here.
You need
to think about this because
these synchronization services
may have the issue
when multiple
users are accessing the same file.
It may be
challenging sometimes.
So, it needs to be
a deep analysis
of the use case and see if it is
the right solution or
what you have.
Here are another solutions, which is
with NodeApp, but NodeApp
provides
an enterprise trust
with high-performance
service for file storage.
So, these ones
on top of
Azure, and obviously, it
has like additional costs,
but it's an option that you
may want to take.
Now, the other
resource that is available here
is the Azure
Disk. So, the Azure Disk is
let's say like the
hard disk of your server
or of your machine.
So, in this case,
in this case, you may
want to, I mean, what
you need to think about here
is if I'm
going to have
a standard
hard disk drive
or an
SDE or
a premium or an ultra disk,
or this is the
IOFPS
how are you
going to have backups?
With manuals and shots
or fundamental or
the service of backups,
you are going to encrypt the disk
in the case, either at
Azure level or at
host level.
So, how are you going to come to that?
And the keys for encryption,
I mean,
if you lose the keys,
you lose the data.
And if you are going to
have Azure in your system,
on the disk,
so you can have like a better performance
access in case
you need your system.
So, depending on the
requirements or the use case,
you may want to choose
which
type of
disk are you going to use.
So, usually databases
or workloads
without concepts of habit are used
in all habits, etc.
So, this is
a performance
sensitive as our
web application
usually go for premium
and what are the
points on whether you have
in-sphere, maybe,
the right option for this
as well.
These are like the
differences for each scenario
the traffic and
the IOPS for
these fixed drives
of the disk.
So, it's important to have them.
And finally,
the security. How to secure
the storage.
So, the most important thing is
to not
expose your storage
account or
either your endpoints to the public
to have policies,
firewall policies, to have
keys managed
for all your data
to be
and the endpoints to be
private.
Another important thing
is the lifecycle.
So, when
you can make
that your storage
evolves
over time, so you
don't have to
so you can
optimize
the costs, usage, and
the access
frequency to that
storage as well.
So, this is like an example
of how to have
some endpoints, private
endpoints to access
the storage, to be
a storage.
And those are the
stuff that we have about.
So, we are going
to do in this case
a study is that we have
our company
with
a requirement of
what to do.
This is page 255.
What to do to design and
storage solution. So,
you need to think that
as I told you before going to
our project, that
we have
pictures,
PDF files,
work office documents,
but also sensitive
documents. And these
need to be
reviewed. So,
the next thing that we are going to
do, I mean the previous
issue is that
how to reduce the
storage costs and how do
we duplicate
the content
and integrate that content
into the cloud.
So, we are going to view the files
located, how
frequently are we
going to access that information.
How to
store that or
set up this storage
for the customer as well.
Also, there
is some exercise
for those who
want to do
the actual creation
of the object or the resource
in Azure.
So, there is an exercise
here to create
a storage account
for these requirements.
So, you can also
take a look into that.
So,
let's do that.
I'm going to put you
in the
groups.
And we are going to
have like half an hour
for this.
So, we are going to
have a full meeting.
And we will
have a full meeting.
So,
let's see.
Let's move
to these
rooms.
I'm going to open those
so you can work.
And I will go
and disappear in a
room. So, let's start.
Okay, hello guys.
How are you doing?
Okay, no.
Okay.
Yeah, it's
perfect.
So, what type of data
is represented in the examples
for this case?
Is that structural?
Not structural?
Okay, you're just correct.
It's not relational.
Those are files.
So, in that
sense, we need to take a look
into, okay,
regarding files.
What kind of criteria
should be used
for the design?
For example, where I'm going to
locate those files?
If there is any compliance
or regulatory
requirements?
What about the performance
of the access in those files?
Am I
going to replicate
the storage in a different
location?
So, I can have
disaster recovery.
So, those kind of stuff
you need to think about.
Also, you need to think about
what kind of service I'm going to use.
Okay, I have the
EFIX files.
I have the global storage. I have the
Azure files.
Which one is
am I going to use the Azure files
for everything?
Or perhaps the global storage
may be used for some of
those files?
Kind of things that are in there.
Try to take a look into that
to see
how, what you come up
with
regarding
that as well.
Okay, so
take a look in. No worries.
We can
keep going for a while.
So,
I'll go to another
group. So, anything
just check it out.
Okay. Hello
guys. How are you doing?
Hello
guys. How are you doing?
Okay. No worries. It's okay.
It's okay.
Perfect.
Right. That is correct.
That is a good idea.
Okay.
Okay. Awesome.
No worries.
Awesome.
Perfect. That is great.
Okay. You're in the right track.
You are doing
perfectly. So, that is great.
So, keep discussing and if you can
come up with a design
you can draw IU
on the icons. So,
that represents this stuff
that you are discussing here. That will be
super awesome. Okay?
Okay.
Okay. Cool. So,
see you later guys. Thank you.
See you.
Hello guys. How are you
doing here?
Hello guys.
How are you doing?
Okay. That is
super perfect. You are
taking notes. Awesome.
Awesome. Perfect.
Yeah. Yeah. That would be
great. I mean, discuss
this exactly
like you're doing right here and try
to diagram that
discussion into
draw IU so you
can get familiarized with
the icon
and how to represent this
idea into an architectural
diagram. Because sometimes
that is like the hard part.
But that is
like the idea. So, try to
create a diagram
representing those
files that you are talking about, those
blocks that you are talking about.
Remember that in draw IU
you have the icons for
office documents, for databases,
for media files.
So you can use that as well.
So yeah. You're doing
great. So keep
doing that and try to translate that
into an architectural
diagram for this
exercise. Okay?
Awesome. Awesome. See you later guys.
Okay.
Hello guys. How are you doing?
Okay.
Do you have your notes? Awesome.
That is important. Perfect.
Yeah. That is
well, is it semi-
structured or un-
structured? What do you think?
Okay. That is correct. Yeah.
You need to think about that.
That is more like structural data
as for these files.
So that is correct.
And okay.
So keep doing that. I mean,
try to take notes into each one of
the points and see where that
applies and what not. And the
idea is that at the end you
can
illustrate
in a diagram,
in an architectural diagram,
the things that you
discussed here. So
remember that you have access
to the icons of
Azure files and Azure Web Storage.
So you can put
that into a diagram and
put in front of
that, for example, a PDF
icon or a
media video icon.
So you can represent
the different kinds of objects
that are going to be this sort here.
And if you want to have
redundancy, you can
use that,
create a diagram to
do that. So try to reflect
the discussion into a
diagram, which is
hard
to express
those ideas in a diagram.
But it's a good exercise
because that is at the end what
is seen and what can be
used when you are
dependent on the solutions
in Azure.
Okay.
Awesome, guys.
I'll see you later.
Okay, guys.
So how is it going?
Wait, wait, wait.
Hi, guys.
So how is it going?
What do you have
so far?
Okay, okay.
Uh-huh, uh-huh.
Okay.
Okay.
Okay.
It's okay. Never mind.
Keep going and discuss and try to
see what fits in and
what doesn't fit. So
see you later, guys.
Thank you.
Hi, guys.
How are you doing?
Okay, cool.
Okay.
Okay. Perfect. Awesome.
Keep going and
we see each other
in a way. Thank you.
See you later.
Hi, guys. How are you doing?
Oh, okay. You have advanced
a lot. Okay, cool.
Okay. Uh-huh, uh-huh. Okay.
Okay, guys.
Awesome. See you later,
again.
Keep going. Keep going.
Oh, Kempis, you're by yourself.
What happened?
Oh, okay, okay,
okay.
Okay, how are you doing?
Uh-huh, uh-huh, uh-huh. Okay.
Awesome. Awesome.
Okay, cool. Keep going and
anything you need. Just ask me
if you need anything. Okay? Okay.
Okay.
Thank you. See you later.
Okay.
Okay, guys.
Let's see if
we are all here.
Okay. Let's continue
with the other classes.
So, who wants
to share what
they have designed or
or no
matter that it is not complete yet,
we can guess
what we have
done so far.
So, go ahead.
Who wants to
share what they did during this
space?
Go ahead, Alexander.
For sure, if you want to, go ahead.
Just charge your screen and tell us
about it.
Okay.
Uh-huh.
Uh-huh.
Uh-huh.
Uh-huh.
Uh-huh.
Awesome. It's a
really good design. I like
a lot that it's super
simple and
that doesn't mean that
it's bad or something, no?
Remember the principle of keys
which is keep it
simple. So,
this works.
I mean, you have
the application
survey.
You have
the backend for the database
with
reputation in multiple regions.
And you have authorization.
It works. It's very good.
Congratulations, guys.
Okay. Awesome. Awesome.
Awesome. So, perfect.
Who wants to share their design
as well? So, we can
enhance and see
what we have
in this
afternoon.
Who else
wants to share that?
Don't make me
call you. You know who.
Ha-ha-ha-ha.
Go ahead
and
charge your
screen and let us
see what you guys have
done. Who else
has a design? I know that you guys
did several designs over there.
Just charge your
screen and let's see it.
Because in the previous design,
it's simple.
It fulfills the requirements.
But you can add
some stuff in there to
make a more robust website
and database
backend for sure.
So, let me show
who wants to share their
design.
Hi, guys.
Let's see.
Let's see.
Marfibel, a lady that
I haven't heard you guys
talk. Marfibel,
do you want to share the design
that you guys did?
Hi. Okay.
She can share it and
you were with the same
team with
Ruler and Alexander?
Okay, okay, okay.
Ah, with Jason.
Okay, go ahead. Go ahead and
share that and let us know
how it is.
Okay.
No worries. No worries.
It's okay. It's okay.
Awesome. Okay.
Yeah, we have.
Okay, so, okay, you have the
first part and the backend. That is
okay. I mean, we all know
this.
Okay.
For Cosmo TV.
Okay.
Oh, I got it.
Okay, I got it.
Okay, no worries.
Okay, okay.
Perfect. Got it.
So, this is interesting because, I mean,
in this design, they are
using Mongo, well, Cosmos
TV as like the main
database and what
they are doing is to
move data from Cosmos TV
to SQL for
the long term. That is,
I mean, that can be done.
Function can be used to
do that. It is correct.
But you
need, I mean, here as
we are part
of the team, I mean,
in real life,
these kind of decisions
are made with the
developers, the architects,
the cloud architects.
So, it's not just only
us who define
or decide what is going
to be in these
solutions.
So, what you
will find usually
in the wild is that
the SQL database,
it's used for
a lot of
the structure of the website,
information,
users, catalogs,
a lot of stuff.
And the Mongo TV
or the Cosmos TV is used for
certain information,
as for example,
sessions or indexing
or search
of web pages
and keywords within
the website. So,
usually what you have is a mix
of both, of those.
So, let me
show you, let me show you
one proposal of
solution
for this
implementation.
This, this
is a,
where is it?
So, here is the
the
OK,
sure. So, one proposal
of solution for this
design, because, I mean, you can see
here that, OK, there is a lot of stuff
in this template
to be filled. So,
they talk about the two regions
for redundancy. So,
that would mean that you
will have redundancy
across regions,
that you will want to replicate
the website.
So, for example,
we are discussing
here mostly databases,
but it
needs to merge
what we had from the
previous case study
with this
new case study. Perhaps you can
add here an Azure files
storage or an
Azure blog storage
for serving
those PDF files and
that stuff as well. So, that is
something that goes here as
well. They always honor the
availability. So, you have always
a replica of the servers
of your vacants.
The database,
they want the database to be high level
and the performance,
the searching pages.
So, this
case
is
almost every time
it is solved
with MongoDB, with
MongoDB, because indexing
and searching in this kind of
non-structured
databases or semi-structured
databases
is way much faster than
a query in a
standard SQL database.
Regarding security, well,
it's the
Active Directory authentication.
So, here is a design
with all the components.
So, the
availability with a traffic
manager that sends
traffic to either
of both of these websites
or just
one website and in case of failure
it sends this to the other one.
The web tier with the app service.
This is something that we
didn't discuss, but it's good for you
to learn about it.
It's a service that is the
Redis Cache or Memcache.
It's another option.
This is a service that
is specifically
designed to
create a session
cache. And what
is the idea of this kind
of cache redis that is here
or Memcache, which is the other
typical product that you see
here. For example, if this
is the web application
for a bank and
the user is here
working
in this, doing some
transactions in this web tier
and for some
reason this server
went down
or this
environment
goes down and
the user that was making
let's say a transfer, a money transfer
a wire transfer.
So the user gets
redirected to this other
environment,
this region and that is
done by the traffic manager.
And the magic that
happens here, sent
to this cache redis
or this Memcache
is that when that
failover occurs
the session
the session
information for that user
regarding what she was
doing
on all that bit things
are not lost
but are
stored in this cache and
they were replicated. So the user
can
continue with
whatever he was doing
and he would not
even notice that there was a change
of location
in the experience
that this person had
on the website.
So that is what this kind of
caching allows you to have
which is super nice.
You can have this
same architecture either
using the caching redis
what would be the difference
that if the user
was doing a transaction here
and this fails
when she is moved or this person
is moved to the other region
they would need to
start over
the transaction as
it has never occurred
because there is no information here
about what she was doing
at that moment. Because as
this person
has not finished
or has not finished
the process, it wasn't
stored yet in many of
these databases.
So that is the function
of this caching redis.
So you can have it in that
which is super useful.
So
going after that is the
data tire. So this data tire
here you have the skilled database
with the
replication. Please notice that there
is a private link
so these regions
are internally connected
are not exposed to the internet
so it is a secure
replication.
And there is a Cosmos DB
for that indexing
for that distribution
experience that they want to remove.
So the Cosmos DB is in charge
of that stuff too.
With the network security groups
the defenses, defenders
so any kids that
happen on the internet.
So this is like an example
of this
diagram
or this architecture that you can
create. But
the approach
it's
what GDB was
perfect because first you need
to go simple. The simple
the better. So the first
actually both
the ones that we saw
are able to
give you something from
working
deployment. So you have the database
you have the web service
you have
redundancy, reputation so you are
good to go. And you can
enhance or build
on top of that so
that is important. So you can
reach this kind of stuff and
please have this
in mind the cache radius because
as I told you is really
really nice.
Okay
so we are going to
jump a little bit because
I want you to
work with the compute case
study because this is huge
so perhaps
this will be the last
module for today.
But let's see if we
are able to
develop another module.
However this module is super
important because this is
like the core of
any solution
in the
cloud. Okay so
this is the compute.
So here we are going to discuss
the different
compute based services
that are available
within Azure. So
the virtual machines as I told
you as we have discussed
are the
most common ones.
Compute services
used in Azure but they
are not necessarily
the feed out
solution.
So
there are additional
options that should
be taken into account
whenever you need it.
So there are
the batch for running
jobs, parallel jobs.
There are the app services that
we already discussed previously.
There are the functions to run
codes, the containers,
the service
fabric for microservices
and the
container, the key
for containers as well.
So
this
is the algorithm
that we already discussed earlier
today. So this
algorithm is super important.
You need to have it
really available
and start to apply it
and over the time you
know which one is better
and why.
So just keep that in mind.
Now, regarding
virtual machines. So
the virtual
machines, perhaps
you can say that
it's simple
because
it's just a machine and we
usually deploy
these machines all the time.
However, when we are discussing
the connections from the cloud, we would
need to think a little bit about it.
How this works. So
from the name,
remember the standard,
the name and the standard that we
discussed yesterday,
the location of this machine,
regarding the regions,
the sizing, the price,
the availability,
the kind of disks that we are going
to use, the image,
if we are going to use an image
provided by the marketplace
or if we are going to use
a system image by ourselves,
created by ourselves,
the operating system
and who is responsible
of this machine, if you
are using Microsoft or Microsoft.
So these are
stuff that needs to be
taken into account whenever
you are choosing
a virtual machine.
So when
you use a virtual
machine, when you want
to test something, I'm going to
give you a super
simple example, but real life.
In my personal case,
I need to,
I mean, I use a
Mac, a Macbook,
so I have OS X
and I need to
deploy a Windows machine
because there is software
that only runs
in Windows. So
I mean, if I can have
a virtual machine on my laptop
but it will take space,
I don't use it like
every
two, three months, wherever, something like
that. So it's not worth it
to have all that space
and sit out in place.
So it's easier just to
access the portal Azure, deploy
a Windows virtual machine,
install the Windows software
that I need, obtain the results
and destroy the machine. So
it's quickly testing something,
finishing up something.
So that is something that
is super useful
in this type of machines.
If you want to do something
really particular,
something that is available there,
like GPU that you can use
from Azure.
If you want to
extend what you already have
but you don't need, you don't want
to purchase
any additional hardware, so
you can just deploy
some machines over there.
The greatest example
was the
pandemic. So,
I mean, basically
all the
clouds
reached
their limits
during the pandemic because
everyone moved
their workloads to the cloud and
it took them almost
a month to recover,
to be able to
provide service
to everyone. So it was really, really
fun that time.
If you want to run
a legacy app
but in a
most modern hardware
or with software or
if you want to quickly
integrate an application, so
these are several reasons
which you want to use after
the machine.
So what is the
deployment?
What needs to be done? So
this is part
of the decision thing.
If you want to give anyone
or if you want to integrate
so the decisions
that needs to be
defined, the network,
the location, storage, the
worries, the monitoring
of this.
There are several kinds
of virtual machines.
The general purpose ones,
the compute optimizer,
the memory optimizer,
the storage, the GPU,
the HPC.
So it's
like its name says it all.
But obviously
this is directly related
to the price of
each one of those
kinds or family
of the machines.
There is a
feature that is not
that widely
known.
It is the virtual machine
spacesets.
These spacesets are
a way to
tie the validity
to the virtual machines.
You can explore your applications
not in one machine
but in a virtual machine
spaceset.
So this will allow
you to increase
the
power
of your application
to have high
availability using
traditional virtual machines.
This is really interesting. This is powerful.
This has
a load balancer.
It allows you to use space.
You can always use the power special
unit. You can define
these availability sets how they are
going to be provided.
You can define which zones
you will be using to have
this high availability
solution. You can
have a way to orchestrate this
kind of deployment. You can have
auto scaling
because it
requires a lot of CPU usage
with the fast-run launch
additional information to
top up with the load
that is being demanded.
So that is a really nice feature
from Azure
for the third year.
So you can take a look into that.
Obviously,
it has a trick.
The application needs to support
this kind of population.
And not all the applications
can do that.
It is something that you need to have in mind.
So you can
have groups of your machines
or you can have a scale set
of your machines.
So this is why you need to
have an alternative development.
This is an
example.
In this example,
you have a real machine
but we are here
going into the
deep end of the real machine
which probably
has a
network into
the sky.
The target size
of the
machine.
They are using climate
feeds.
It is using
launch monitoring.
This is like the
full design of the result of the thing.
And those are
the complete services.
Well, those are the
complete services.
There are these
complete basic services
that I will be showing.
The ones that we will be discussing.
These are the ones
that are in the webpacks.
The last ones.
The last few three months.
And the other component
that is required
in this kind of stuff
are the virtual networks.
The virtual networks are
the cloud network
for the
deployment.
So these networks can have
public endpoints
that can be accessed
from anywhere on the internet.
Or find out endpoints
that only can be accessed from the network.
You can have
solvenating inside the virtual networks.
And you can have
connections to these networks.
And you can have
a design of
the virtual network inside
the cloud.
And you can have
a VPN network
that can be accessed
from the network.
So,
the additional
network you will find
different networking services.
For example, VPN networks.
So you can have a VPN network
that gives you access
to a virtual private
network in the cloud.
And in order to access
you will need
your on-premises
location.
An endpoint for an IT set VPN
to establish a tunnel.
So you can
route traffic
from on-premises to the cloud
and vice versa.
And here is something that
it should not be overlooked.
But it is the
subnetting
of both your
on-premises network
and your cloud
networks. Because
if you
make the rookie mistake
of having the same
subnet here
on-premises and
have that same subnet
here on the cloud,
you won't have communication
between both networks.
Right? Because there will be no way
of routing those packets.
Because it is the same.
So you need to think about
how to route the traffic
between
those
components of this
packet as well.
There is another
solution that
is the
ExpressBot. This ExpressBot
is an
endpoint that is provided
by Microsoft
partner, usually
a data center that has
a direct connection
to Casio. And they
are able to give you access
so you can have
either
a typing connection
for you, for your company,
to access all the
Office servers, services,
the public
and key addresses of Casio,
and all the traffic for you
on your network. So this
is like a private connection
that is provided
by a telecom
vendor that has
this kind of arrangement
to enter in the country.
In particular
in the area at
the end of last night's connection.
Another service
that is available here is the
DNS service. This DNS
service has
the
ability
of
this
salt, the DNS
or the FPDN
events that you have created
for the services that you are
exposing to the internet.
So those are like
the way to reach out
to these
services for the internet.
There is another complete service
that is the patch.
This patch is usually
used for high performance
computing, but
it can be used for
other kind of jobs
that you need just to check
the currency. But the
idea is that this is something that
requires like
a high intensity or high
power of complete
power of presenting
the data.
And then just once that
job is executed, you
reduce the matching and you don't use it anymore.
So that is like the idea
of this patch processing
solution. So it depends
on the industry and the use case
in particular. So those
are not that common.
Just in the specific
industries
is where you can see this kind of stuff.
This is an example.
The movie
industry is a big user
of this kind of solutions.
So all the rendering
of 3D images
can be done
in this kind of stuff.
So the rendering,
you know that rendering a 3D
image or 3D video
can take hours
of computing power.
So this
is those kind
of solutions that
that kind of stuff.
There is some
machines that
are available within
within
Azure that are
well suited
for this kind of
jobs in the sense
that are machines
that can
use or
have a set
usage for
a specific
or a short period of time
and then just
don't have enough power
to be used at all
or to be used in this kind
of tasks. So
these are machines that
don't
quarantine the same level
of performance all the time. So
those are cheaper
than other ones.
But it may adjust
for your systems
better because
as they are no
quantity of performance, it can be
way cheaper than
any other
kind of machine that is available.
Also there are the spot instances
which are similar.
So the spot instances are
like some
I forgot the word.
When several
users
compete for having
access to the compute,
they make offers of
how much they are willing to pay
for having
that compute power
and regarding
different offers,
the price is settled
and that way you can buy
or have access to this
compute power. So
this is like having dynamic
pricing.
Obviously it can
increase but also it can
decrease. So this is another
case
for this kind of workloads.
Another
compute solution is the container
systems. Although this
was
depreciated so it's not
that used but this
container
is just a simple way to
launch a container and make it
run. I should.
So the containers are much
more lighter than
a virtual machine
because they just have
the image and the
container portion of the image
to run and the virtual machine
has like the full
operating system so that is
heavy work.
This is an example of
how to have
a pipeline
similar to the ones that we deployed
previously. So
in this case they have the container
registry and they are deploying
in this example
Kubernetes services. Those
containers. These can be replaced with
container instances
if you only
have one or a few
images too.
And Kubernetes
which is like the
most common. Well
not necessarily
the most common but it
becomes more
and more mainstream every
day. So
it's becoming
the factor
way to launch workloads
into the cloud because
the Kubernetes has
the feature
to be cloud agnostic.
So you can deploy
on top of Azure Kubernetes
and you can
do this same deployment
in Amazon
or in Google.
So you will have cloud
support,
for cloud support
and you will have a
like and you
will break the vendor
working that comes with the cloud.
So that is why it's being used
more and
more often.
Another feature that
comes with Kubernetes is
the high
availability by default.
So with Kubernetes clusters
you have a complete
and high availability.
And if you merge
that with the storage
and the replicas
you will be able to have
multiple clusters in different
regions providing
service to your applications
with the backend fully
replicated as well.
And also there are
the functions. So these
functions are
serverless applications
for executing
for example
a web service
or an
event
for an event
to execute an event
within your system.
So when to use
Azure functions?
When you are running something
short term?
So the main
characteristic of the
Azure function is that
you, I mean this is
something that is supposed to run
for no more than
10 to 15 seconds.
If it
if the execution of
your function requires
more time than that
this is not your solution.
So you need
either to resign
the function to be able to
finish the
execution within that
time frame, 10, 15 seconds
or otherwise
you need to choose a
container or an app service
or a different solution to run it.
So this is
important because this is
really useful for small
stuff that you may need to
do or to have within your system.
This is
an example of using
Azure functions in this case
is to use
different features of the
AI services
for translation
or vision or
recognition within
the cloud. It's an
example. There is another
example here with classification
of documents with
Azure. So those are
reference architectures that can be
used. And in this case
is for functions
in this case
it doesn't show but
what this does is
just like a function running
interacting with some branches
of a
specific one as well.
There is
an additional
kind of function
that is the Logit app.
So these Logits apps
are
workflows
with Logit workflows
which are figured.
So for example if a message arrives
this Logit app
will
for example send that message
to distributed
lanes or
it will either send
a tweet
or send a record to
Dynamics or
send a file to Dropbox.
So those are the
Logit apps that are available here.
So this
decision tree
allows you to
decide if you
want to use or not
a Logit app for your service.
So this is
a great way to integrate
these
different systems
that are
not necessarily designed
from the beginning
to be integrated
but you may need to
do that. I mean you want to store
every tweet regarding
the product
launch that your company
did last week into
Dropbox
resource because
the marketing people want to
share those tweets just to say
that's all. So
it's a way to do that
and integrate.
These are some reference architectures
on example 2 for
2019
and the comparison between
Logit and Logit apps
and functions.
So Logit apps is more
low cost, function
it's cost.
So those are
ones of the difference.
And this is like
mostly to connect
different
platforms and
this is now for events.
And this is an example
of using functions
we in this case
are sharing location
service. So
it's used here
as well.
So the connection is here.
So here is our
case study.
Here is this
again the decision piece
so you can take a look into that.
And in this case
the case study
is has
the idea here is to design
a full
flesh app
solution
for this company
because you require
to have a phone in
a file
as a phone in
which you will have the web application
or the stuff that needs to be
in front of the system.
And there will be
a middle file in which
you will deploy the functions
and the backends and all the stuff
that is required by this
solution by this application.
So this is the
example of the
solution.
So there is
an application
that requires some
servers, some
point users like in .NET
and some databases.
This application
has a heavy demand.
The servers can reach their
performance limits in the same
day but the servers
are still still
doing up hours.
So
what should I do
or what should I use to provide the service?
Here are
the middleware
with six API calls
from the phone in
and all the time depending
on the workload that is here.
We will vary the workload
or the demand of these services.
And the
SQL server that requires
a sign-up
to the best
performance available here.
So which
service, which complete service are
you going to recommend for each
one of these dials?
And try to create
a diagram to explain this
solution. You can create
a few kinds
of solutions for this.
There is a lot of
options. So let's
do this.
This is like
386 up to
388. So I'm going
to
put you guys in the
break-up
room.
Let me see.
So let's
work with the
with this
and the sign-up solution.
So this is the decision tree
so you can
decide what
will be
useful here.
You can use check field
to discuss as well
to help you decide.
So go for it
and let's give it a try.
We have a
USAID
that will be
like 45 minutes
in total for this
app. So
I'm going to send you
to the break-up rooms. And I
will meet you there in a while.
So go on.
Hello.
Hello guys. How are
you doing? What have
you found so far?
Uh-huh.
Okay.
Okay.
Okay.
Okay. You can
add, I mean, it works.
It's simple.
You can enhance this
adding some
replication to your database
back end so you can
be resilient to
failures as well. But yeah,
it's good. Okay.
Okay, guys. So
let's keep working and
see you in a few minutes.
Okay.
See you later.
Hey, guys.
I cannot
see your
screen.
Yeah, it's
okay.
Okay. Yeah.
Now I'm watching.
Oh, awesome.
Okay. That's nice. So
tell me about your design,
guys. Let me know how it is.
Okay.
Sounds really
good. Sounds really good. Okay.
So
okay. Keep working
on that and we will meet
later.
Alright.
So see you in a while. Thank you.
Hello, guys.
How are you doing?
How is it going?
Awesome.
Awesome. Let me
see it. Let me see it.
I'm not seeing this.
Okay. Okay. Okay.
Cool.
Oh, this is
really good.
Okay. It's really good.
I like it a lot. This is a good
architecture, guys. Very
good.
Okay.
Well,
the service public usually
is more like for
messages and queues or
when you are doing
integrations.
So actually, actually,
what is happening
is that it's been, I mean,
what was used to be
deployed on top of service public
is now is being deployed
on top of QNets.
It's what is happening, to be honest.
But yeah, because
it's a service bus
at the end. So it's like
an integrator.
Exactly.
That is correct. That is correct.
Awesome. Awesome. Okay.
Cool. Okay. No worries.
So see you later.
I'm there for sure. I'm going to
ask you to show
your design, guys, today.
Okay?
Okay. See you
nowhere. Thank you.
My teams,
it's been a long time to
join.
I cannot see in the future.
Oh, this is a cool design.
I like it. So talk to me about it.
Let me
see how it is.
Uh huh.
Okay.
Okay.
Let me see the
lathe tire. I'm not
being able to see the lathe tire.
Okay. So you have
a lot of lathes there.
Okay. Okay.
The back end is a little...
Okay. It's okay. It's simple.
You have the three tires
for the front end, the middle tire,
the back end, and you're using the end.
Okay. Cool. So
awesome. So
we are going to go back to the
main room and we're just going
to expose both
the
designs.
Okay? So see you in
a few minutes. See you.
Okay, guys. Welcome
back. So...
Awesome. I saw
the designs and
I have to say that
I mean, almost
yeah. I would say that all
of the designs are different
to each other and
they are really good.
So that is super cool.
Please, please do share
all the designs that
you have done so far in
the chat so that other
your other colleagues can
take a look into what you have done.
So
we can like
spread the additions that
we have.
So I would love if you
guys can
take a few minutes to
expose the
designs that you
have made.
So first the
one, I'm not sure if
Kevin or Lynn
who is the one who has
the
the
diagram. So
to show the screen and explain what you
guys did.
So John or Kevin or Lynn
or Pierce,
whoever you want to show
the screen and explain it to us.
Okay.
Yeah, we can see that.
Okay. Okay.
That is good. Okay.
So please guys, this is
a straightforward
design that has
two main levels.
Perhaps what I
will suggest you to take a look
is into the middle tier
that perhaps it will
require an additional
service or a function or
a microservice to
run that
.NET application that
is being discussed
in the case. But it
works. I mean, you can
have this and make
this happen for sure. So
thank you for
sharing. And let's
go to the team two to
see their design. So
I'm not sure if Jason or
Marfield, if you guys
have your design
and want to share it or
Lynn and explain what you did
guys.
Okay.
Yeah, it is
there. So okay.
Let's walk
through it.
Okay.
To you. To you.
Okay.
Okay.
Okay.
Okay.
Okay. Okay.
Interesting. Interesting.
This is an interesting design.
So please be sure
to share that again
with your colleagues.
Okay. Thank you so much. Very good.
Now let's see
Alexander
or Blair or Amitri
Charmaine wants to expose
the solution that you guys
designed.
Okay. Okay.
Okay. Perfect.
So is the three
tires, the
service for the
website,
the middle tire is
over nets with some IP
gateways to access those services.
Okay. Perfect. And the
databases with
a redundancy
replication,
cross replication. Okay. So that is
super cool as well. Okay.
Guys. Very good. Very good. So
let's see the last team.
So Kevin, Kempe, Piers,
whenever you're ready,
want to explain
the design. Okay. Thank you.
Yes, I think we, yes,
we can see the results.
So please
guys pay attention
because this design adopts
a different approach
to what you have done
previously and it's valid.
I mean, it's not
as I told you,
there is not a
bad or a good solution. So
just different approaches.
And the idea is that you can improve
and build on top of that. So
go ahead and explain that to us.
Thank you.
Awesome. Awesome. Perfect.
Very good, guys.
So what happened?
Okay.
So this approach is
using more like a traditional
approach of using the
designs to deploy
the different workloads
at each one of the tiles.
So very good indeed.
So please share the
designs and let me show
you
two proposed designs
or solutions for this
case study.
So you can have also an idea
of a different
approach to
solve
or to solve this
case.
So
here, so the
web servers, the
middleware with that
net and
the backend with the serial server.
So in this case, we
can have an
infrastructure as
a service solution,
which actually is the one that
was just being exposed
by
Kimpy.
So it's kind of
like the same
proposal that
this team did.
So in this case, with
infrastructure as a service, they have
a load balancer
with a frontend running in
a set of
real-time machines.
And also
the middle player will have
another load balancer. And again,
with the
virtual machine as a set to handle
the load. And finally,
another load balancer
with SQL virtual machine
running the backend.
It has like a storage
account
and the authentication
directory. But notice please
that it is the same
idea, the same
approach that was done
by Kimpy. So it's very valid.
Obviously,
this is like your first
exposure to Azure and
all that stuff. There is
a lot of things that can be
drawn from these days.
One of those is the
the item set, the use of
the item sets. There is
a specific
item set that needs to
be used if you want to represent
the state set. So
you can dig a little
bit, explore a little bit. So
you can have other idea
how to use those. However,
in Azure, you
can have exactly the same
architecture
that is here. But in this
case, you can see that they are
using just virtual machines,
multiple virtual machines.
But it's like the same
example of the state set.
So this is one solution.
Another solution
that is proposed here
is kind of similar to
the one that was
proposed by two of
the teams that we saw,
that we discussed.
Well, actually the other two teams, I would say.
Kaina, because
there were two teams
that use microservices
with Azure Next, which is super cool.
And it's
a valid option.
Hold that thought.
I'm going to discuss a little bit about that.
However, just to discuss this
part, this approach,
which will be like a platform as a service
solution,
it's using, well, the
gateway and the app services for the
command. And it's using
function apps for the middle
world for the
webnet application.
And then again, there is an SQL
database for that
storage of things.
This is like the same design that we've
presented. So this is another
solution.
If we take a look into
what we have done this
last hour,
we came up with
about five, six different
solutions
that fulfill
the requirement. Obviously,
we can improve, we can
make it simpler, we can make
it more complex. But in the general
idea, we have different
components that are in there.
Now, regarding Kubernetes,
Kubernetes,
I mean, personally, I
really, really like Kubernetes.
I find it really
attractive.
It's really beautiful.
However, Kubernetes
may be sometimes
of,
I mean,
of what is needed over
another complex
solution to what is needed.
So you can have
the same solution
simpler and less
expensive than using
Kubernetes. So with the Kubernetes
requires a really deep
infrastructure in order to
to completely work.
So sometimes, I mean,
it is
useful when
the size of the application
is big enough
and complex enough to justify
the use of Kubernetes.
And the reality is that
the big amount of companies
that are moving into the cloud
that are modernizing their
services, they are
not yet there. They are just
starting.
And so
there is still like a,
obviously, there are companies which are
big enough that there is
no other option but to use
Kubernetes. However, there was this
study from a few
weeks ago that found
that you can, in
general,
the Kubernetes clusters
are over-provisioned. So
people are using more
nodes that are already needed.
So they are wasting
money.
Without the needle, I mean, they
can be more
adjusted to the
requirements.
So that is something that
has a lot of stuff to
think about.
Anyway, those are different
really good designs that
you can work with.
And what we're going to do is
we're going to have a small
talk with Ray for 10
minutes. And after that
we're going back
just to wrap up and
finish
today's session on the
training.
And so
let's meet in 10
minutes. Okay?
This is my
talk.                

on 2024-03-04