Here and welcome back.
Now in today's we will be discussing about the basics of Elastic Bienstock service.
Now, the best way to go ahead and understand the importance of Elastic Bienstock is to compare the
traditional deployment approach with the elastic Bienstock based approach.
So let's go ahead and take a simple example, best use case where you want to go ahead and deploy a
simple Hellewell application for the production environment.
So generally, what happens?
And any time a user visits your website.
Hillshire Hello message.
So this is a use case.
Now, generally, whenever you're deploying an application in a production environment, there are a
lot of services and a lot of different deployment approach that you need to use.
So for an example, you might need to use two instances where the application would be hosted.
You need to create an auto scaling group so that when the Law Order traffic increases, the two instances
can also scale up.
Apart from that, you also need to use the elastic load balancer so that the traffic can be split across
multiple easy to instances.
You might need to use cloud watch so that the logs from all of the easy two instances can be analyzed
centrally.
You might need to use around 53 for DNS related use case in this application and so on.
So when you want to just deploy your application in production, you see that there are so many services
that we need to create from the ground up.
And this leads to certain challenges, specifically for startup who do not have a dedicated development
team that are available.
So in the newer approach associated with Elastic Bienstock, again, they use cases the same and all
we have to do is we have to create the correct elastic Bienstock environment.
And once this environment is created automatically Elastic Bienstock will go ahead and create the underlying
resources for us so it can creatively be easy to auto scaling cloud, watch all the necessary web server
configurations and so on.
So this way it becomes very easy even for developers to go ahead and deploy a production grid infrastructure
while he can go ahead and just upload the application for it to be up and running.
So again, at this moment, it might be a little confusing.
So let me quickly give you a demo to understand more on it.
So currently I am within the risk management console.
Let's go ahead and type Lastic Bienstock so we'll select the right service from you.
And this is the primary new console based on Elastic Bienstock.
So first, let's go ahead and create an application within the application.
Let's just quickly give it a demo haven app and within the platform, depending upon what the code is
based out of so called can be based on BHB, Java Tomcat and so on.
So depending upon the code that the developer has written, he can go ahead and select the right platform.
So for an example, let's select BHP and within the application code there are two options for us is
either a sample application or second is upload your code.
So in case, if you have written a BHP based code, you can select upload your code and you can click
on choose to upload the career for simplicity.
As of now, we'll just use sample application here and let's go ahead and create the application.
So as of now are elastic Bienstock environment is in the creation stage, so you'll see that it is doing
a lot of things behind the scenes.
So it is going ahead and creating the load balancer and its associated configuration.
It is going ahead and creating security group.
It will go ahead and create easy two instances and so on.
So depending upon the resources that are required, it will automatically go ahead and create the entire
set up for you.
You would no longer have to manually go ahead and create each and every resource here.
And this is the beauty of elastic Bienstock.
So let's do one thing.
Let's quickly wait for a moment here and we'll resume once the environment is created.
So currently the environment is still in the creation process.
But I just wanted to show you a few things.
So at 350 ppm, the environment creation was started, it went ahead and it created various resources
like security group.
You see that it has also created or deskilling group.
It is creating an easy to instantiate.
So if you is he is doing since has been created, it is creating a cloud would alarm as well.
I don't load balancer related configuration is also done and now it is going ahead and creating the
rest of the environment required for the application to be deployed.
That's great.
So it took.
Two to three minutes are not in their application got deployed.
Now, it has also given you a sample earlier.
So if you just open up the sample you added, you will see you basically get a congratulations.
And this is the application that was deployed.
So essentially from the elastic Bienstock level, all that you need to focus is to create an elastic
Bienstock environment.
You do not really need to worry about how to configure Elby, how to configure or scaling group, how
to configure cloud, how all of these things are integrated and so on.
So you can only focus on either using a sample application and introduction, uploading your application
and that's it.
So basically you have option to upload and deploy where you can go, then upload the application.
So this is the beauty of elastic Bienstock.
That's great.
So I hope at a high level overview you understood the importance of Elastic Bienstock based service.
Now, one more important thing that you need to remember is that Elastic Bienstock not only creates
the infrastructure, so infrastructure was one thing, but it also creates a lot of things like Web
server configuration, primarily because this application is deployed inside a single instance.
So how exactly a BHP application needs to be deployed inside the U.S. to instance, what are the BHP
related packages that are required?
What are the Web server related softwares that are required?
So a lot of things happens behind the scenes, both at the infrastructure level as well as the easy
to instant's level.
And all of these things are taken care by the elastic Bienstock.
So with this practical basic, let's go ahead and quickly revise the concept of elastic Bienstock.
So it is elastic.
Bienstock is easy to use service for deploying and scaling web application and services.
So now we have seen on how easy it is for a developer to go ahead and upload the application and his
whole production infrastructure is created for him.
So all you need to do is you have to simply upload your application in the Elastic Bienstock and everything
else from capacity provisioning, load balancing health check and deployment is taken care of by the
elastic Bienstock environment.
Now, let me also show you a few more things.
So if you'll quickly go the easy to console, so you'll see that you have easy to instanced that is
running.
So this is the primary instance which is hosting your application as of now.
And same thing.
If you'll go to the load balancers here and you see one load balancers automatically created and this
is integrated with the easy two instance that has that application.
So this is the basics of Elastic Bienstock.
So in case, if you want to go ahead and terminate the environment, in case you intend to do the practical,
you can all you have to do go to actions, just click on Terminate Invermay, you'll have to give the
environment name, which is the most pyefinch EMV and click on terminate.
So now if you look into the events here, it went ahead and deleted cloud watch, deleted load balancer,
auto scaling group and various others.
In fact, if you go today, you see two instances just to quickly verify.
Let's refresh the page and you see the instance.
Data is not terminated.
That's great.
So that's a very high level overview about the elastic Bienstock service.