 So dear students, this module is in addition to our continuation of the previous module. In the previous module, we were talking about how do we make an application connect to the database? What type of solutions do we have at our disposal to make that connection to the database? Of course, there are many, many techniques and tools and technologies are there. And we have to focus on the ones which are more relevant for us. Let me first give you an overview of this module and then we'll go into more details. And I will also talk about the strength and the weaknesses and the shortcoming and the issues of the two techniques that we will be discussing in this module techniques or the methodologies. So we'll talk about the template driven approach. Okay. And we'll talk about the GUI graphical user interface application developer approach, both have their benefits and their shortcomings. Both have their clientele, both have their users, both have their people likes and dislikes. Let's go into more details. The benefit of the template driven approach, it simplifies web based programming. It simplifies how it simplifies. It consists of multiple components. HTML and non standard tags are there, which help you create that wonderful application. We have the template parsers at our disposal. And of course, database client demons are there. Demons are small programs, which are running in the background. So that helps in that template driven approach. But there is a problem. There's a catch over here. The catch is their product dependent. Product dependent means that I would not like to name any company or a product, but certain companies certain ecosystem they work. And you get accustomed to it, you get used to it. And then the migrating becomes difficult and expensive. How and why because it has to be rewriting, rewriting the database access, rewriting the flow, rewriting the control. And of course, when you rewrite it, you will make mistakes, and you will run it, and you will debug it, it will take time, any effort resources. So they has to be trade off. Okay, so the benefit of this template driven approach versus portability versus migration, you have to consider this before selecting one, there's nothing bad or wrong about it, but you have to be careful. So if we summarize the benefits and shortcomings, you can quickly develop and access the database in a couple of hours. If you have properly installed this application, okay, this template driven application, it will not take long in a couple of hours, you can have your database access, the results being shown at the client end. But the remember is there are certain things which are important to that company which may not be aligned with your importance. Okay, so they have limited flexibility, and they have and they don't support complex operations, because it's their choice. And it's slow response is there because of heavy string manipulation, the performance is also degraded at the ease of use. And you have to test you have to evaluate before you rule out whether you're going to use it, you're not use it. And this testing and evaluation is going to take time, money, resources, people. And finally, remember that development time and expertise, they are more important than speed. You can have a quick running application running very quickly, right. But if it doesn't support expertise, you don't have a system which last long. Now let's look at the other approach. GUI application builders graphical interface, mouse click application building and management, the programmers who are used to working in a graphical environment point and click, this kind of application is for them. And this application generated using ODBC or API or database net protocols. And the benefit is that usable and configurable APIs are generated. Okay, the API is generated, you can change them, you can customize them, you can use them. And this is the benefit. And there are many, many options are there. CGI API, they tend to be open. We see that they are benefits of this approach also. The biggest benefit is mouse click point and click, very, very limited programming. So if we summarize the benefits and shortcomings, rapid application development, we have lectures, two lectures about rapid application development, which will be covering very soon. And then is the shields developer from low level details. What happened when the the programmer is shielded from low level details, then the programmer is more productive, developing a nice, useful application. Okay, web application. That is the thing. Now, as a result of this GUI base, you have kind of a fat code. Fat code, fat code mean you have a lot of code, which is automatically generated and which results in flow execution. And then of course, there's a cost also. So for one of kind of a development project, the GUI based approach is kind of expensive, unless of course, you will be using this product for a number of applications, which you will be developing over a period of time. That's all I have for this module. Thank you very much.