 Hello, everyone. Myself is Supriya Ambarkar from Walton Institute of Technology, Solapor. Today we are going to discuss a topic on Google App Engine. This is a software that facilitates the user to run his web applications on Google infrastructures. The learning outcome. At the end of this session, students will be able to learn the working of Google App Engine platform. Also, students will be able to identify the various advantages of Google App Engine. As an introduction, Google App Engine was first released as a beta version in April 2008. The Google App Engine is a platform as a service that is in pass. It is for developing and hosting a web applications in Google managed data centers. The Google App Engine opens Google's production to any person in the world at no charge. Google App Engine is cloud computing technology. It is more reliable because failure of any server will not affect either the performance of the end user or the service of the Google. So it virtualizes applications across multiple servers and data centers. Other Google Cloud-based platforms include offerings such as Amazon web services and Microsoft Azure service platforms. So there are the list are there. Now we will see what is Google App Engine. App Engine lets you build and run applications on Google's infrastructure. App Engine applications are easy to build. App Engine applications are easy to maintain. Also, App Engine applications are easy to scale as your traffic and data storage needs change. So much like Google gives us all free email with an amazing amount of long-term storage. We now have the ability to run the software that we run in Google's data centers. Now we will see why there are various reasons for using the Google App Engine. Because of it is an easy to get started, there is a preliminary definition of this App Engine in terms of it is an easy to get started. So anyone can get started with this particular applications or this particular platform. It having an automatic scalability. As per your need, we can easily scalable one. Automatically, it is having a feature. Reliable, we can say it is having more reliability in terms of the other. Performance is good. We having lots of the performance in terms of the calculating this particular App Engine's performance ratio. Security, we can say it is an secure one. It's having some kind of a credentials. It's having an authentication. And apart from this, we are having a whole purpose for solving our deployment of an applications using this Google App Engine platform. Now we will see the different features of Google App Engine. First, there is in popular languages which has been introduced by this particular platform. So you can build your applications in using Java, Ruby, Node.js, then the C hash, Go, Python, or PHP, or you can bring your own language at runtime. So this is the more popularity in terms of the App Engine. Second one is in terms of then it is an open and flexible one. So it's a more important feature of Google App Engine. Here the custom runtimes allow you to bring any library and framework to App Engine by supplying a Docker containers. So this is an open in terms of then flexible one. So then third one is fully managed. It is a fully managed environment which lets you focus on code while App Engine manages the infrastructure concerns. The next one is in powerful application diagnostics. You can use cloud monitoring and cloud logging to monitor the health, the performance of your app, the cloud debugger and the error reporting to the diagnosis and the fix the bugs quickly. So powerful application diagnostics is there. Application versioning. You can easily host different versions of your app, easily create development, test, staging, and production environments. Next one is in traffic splitting. Traffic splitting means route incoming requests to the different app versions. So splitting is there. Next application security. It provides a safeguard to your application by defining access rules with App Engine firewall, by default on your customer, the domain at no additional cost. So it is an having insecure one. Then the last one is in services ecosystems. Tap a growing ecosystems of Google cloud services from your app, including an excellent suit of cloud developer tools. So these are all the features of Google App Engines. Now we will see the hierarchy of an App Engine. So this diagram illustrates the hierarchy of an App Engine app running with multiple services. Here in this diagram, the app has two services which contains multiple versions and two of those versions are actively running on multiple instances. The App Engine app is created under the Google cloud project when you create an application resources. The App Engine application is a top level container which includes the service, version, and instance resources. That helps you to make your app, when you create your App Engine app, all the resources which you want to create are created in a region that you choose. And including your app code along with a collection of settings, credentials, and your app's metadata, every App Engine application includes at least one service, the default service that can hold as many versions of that service which you like. So this is in one kind of a hierarchy. Now we will see the overview of an Google App Engine. Here they have designed in terms of the three different separation, in terms of the support services, middle and cloud computing services, and top most is on client capabilities are there. So in terms of then support engine services, we're having in GAE data stores, GE data, Google accounts, social graphs, APIs are there, and some other services are there. So in terms of the cloud computing service, we're having in this Google App Engine platform, we're having in different kinds of the languages like a Python, the dynamic, scalable runtime environment is there. So this is in terms of an Google App Engine. Then in terms of then client capabilities, we're having in Google Web Toolkit, mashup editors, Google gears are there, Google gadgets and others are there. So in between these three different, whatever the categories, we're having in some kind of an integrations. So we want to launch a particular app, we want to launch a particular, deploy a particular app. So we're having in facility and integration between them is necessary. Now pause the video and write down your answer. Why there is the need of Google App Engine? The answer, the need of Google App Engine is because of it's a lower total cost of an ownership. It is having a rich set of APIs, fully featured SDKs, software development kits are there for and local developments, and it's having an ease of deployment. So you can easily deploy your or integrate your particular application with the help of this Google App Engine. So it's having a more popular Google App Engine in terms of this all necessary needs. Now we will see the differences between the, one more App Engine in terms of then, which has been developed by the Amazon. So we will see the some differences between the Google App Engine versus the Amazon Web Services. First in terms of then cloud services, it's having a focus in terms of Npass. AWS is in terms of Npass and us. Virtualization platform in GA is an application container. AWS, the OS level running on a Zen hypervisor. So this is an virtualization platform. The next point is platforms supported, which platform is going to support for GA? Linux Windows Server 2008 for Amazon. Linux Windows Server 2003, then then Open Solaris is there. Then then control interface. Here is an API is in control interface. Then AWS API command line is there. Storage, Bigtable and MegaStore is there. For Amazon, simple storage and the simple DB is there. Language supported in both Java, Node.js, PHP, Python, Ruby and so on. Load balancing for Java, a Google App Engine is an automatic and in terms of then Amazon it is in round robin. Data after termination, the Google will not take any action for 90 days after the effective date of termination. But in terms of an Amazon, it will not take any action for a period of 30 days after the effective date of termination. So these are the basics. The differences which we are able to suppose to consider for GA and the Amazon. Now, few points I want to focus. If your application can be architected to run within the limited Google App Engine runtime environment, then take the advantage of Google's lower hosting cost. And if you need a more flexible environment to deployment platform, then Amazon is good solutions. So GAE has a lightest admin load as compared with an Amazon. So you don't worry about how many servers your app is going to use, how to share a data, how to load balances there. So in terms of that, we will prefer the GAE. Now we will see the different advantages of Google App Engine. Here you will be getting the infrastructure for security purpose. It is an scalable one, easily scalable. Performance and reliability, we having that particular point, cost saving. We doesn't want to take to buy a particular hardware. We doesn't want to make a setup. So a readily available setup is there. We just want to take that particular cost-saving advantage. So in the platform independence is there. There is no any kind of restrictions like a language. It's having in platform independence. You can deploy your application in which language you want to prefer, which language you want to like. So platform independence is there. So these are all the advantages are going to focus for the Google App Engine platform. So we want to think. These are the references which I have referred for this particular topic. Thank you, one and all. Thank you.