4 hours 39 minutes
welcome to lessen six point to where we're talking about continuous deployment specifically around the cloud. Describe ah, quick lesson by just one kind of delve into a little more or expand a little bit versus looking at Jenkins from the perspective of, or any of these others from just a local running tool.
We'll look at some of the cloud based delivery and and specifically discussed 80 P. S cope codepipeline and describe bashers version of it APP service.
So cloud base is not limited. Local. As I mentioned where we were using Jenkins or there's get Lab.
There's these cloud based services, which offer the the full pipeline so he, instead of running their own your own tool, you can run Jenkins and get lap in the cloud. But instead of running your own tool, managing and updating it, there are these cloud based services which may integrate as well are better if
you are you. If you're developing your app
specifically in one of those environments where you're not having to then pull code from one place to put it, another to deploy here. If it's all in one place, it might might serve your organization Well,
AWS has codepipeline. What they have is their elastic beanstalk, which is the application server that runs whatever code you're gonna be deployed have several versions that they support.
But they also have our container service
and they have specifically they have community service. So even if if you even want you to want to run kubernetes or ah Docker specifically,
you don't have to run that environment either. You can have this completely late cloud our service base
that offering from them from a to B s and just run that Run that again. You don't have Teoh
update it, manage it. You can let the experts do it.
And as your has, has similar services they have the APP service. They have containers as well and they have their own a ks for running kubernetes
A quick question for you. How would you choose a deployment platform if you were said, sign when you want to run locally or in a cloud and which one?
So there really isn't a simple answer that this because it's not. Here's this thing, this spreadsheet. Uh, first you Maybe when I look at, do you have any expertise already in house, Or do you have to go out and get somebody at that point? If you have somebody in house, it may save some money. But else need to look long. Term
is your if the expertise in some niche product that
may not scale way scale well, or that may have a limited expertise out there. So even if you have expertise, if they leave, it might be difficult to find new people
and isn't on a scalable platform against the same thing are you are using some product that not many people use. It might not be open. Source. Will you have problems down? The lines are really look at all these ideas together and pick the best one that that suits your enterprise. As I mentioned before, maybe you might be already be developing
in the cloud
in a specific environment. Might one look at those services first,
and as I mentioned it, it it's if you are in the cloud or even specifically maybe a mobile app that that's tied to one of the providers. It may not make sense to look at some completely different environment that might have some a little bit more
service offerings, But then you're going to spend a normal, enormous amount of time or money trying to switch over.
So here's an example of a TBS codepipeline. It's a very simple example just to kind of get it on a screen shot where they have their being stock
application server. So when code is committed, it triggers a deployment and goes through these different phases, just like the pipeline were using political build test deploy. He would obviously put more test in here.
You can hook it, Teoh get hub. So this one triggers that
that this full pipeline, once it's committed within get hub and mentioned there you can even put it in a BS has their own codecommit. You know, when he is that you can put it in an S three bucket. There's multiple different ways you can have the code where you have it stored,
as it has a similar service. It's their software release pipeline. They call it the they're built services called who do where that you can do dot net PHP node python. It's the same with with a DBS is they have job PHP several different being stock deployments. So you pick that.
And it knows this is what The application server I need to spin up
there, as you're also has their own pipeline service and say, very similar. You condone they they support get, huh? Big bucket, The azure repose. So both of these
offerings are very similar and what they offer
so quick. Quiz
as your pipelines can deploy more than just Windows applications running dot net. Is this true or false?
This is true. The azure pipeline support C C plus plus dot net node all of these services. So if that kind of not associate Microsoft Azure with Microsoft applications, they support many applications here in the full stack to help run that.
So we looked at continuous delivery specific to some cloud offerings. In this lesson and next, we'll take a look at infrastructure as a code.