 So students in this module, we will look at 10 web development frameworks, five of them are for the front end and five of them are for the back end or the server side. Now of course, we will look at some of the most popular web development frameworks in the market. And how do they what are their pros and cons? What are their strengths and their weaknesses? So we will look at all of them for the five front end and for the five back end. And of course, I will also identify what is the characteristics? What are something special about those frameworks? And I will also talk about that across these frameworks, what things makes a framework popular or mostly used and what are the things which are not so much technical, but which are with reference to the usability also, which makes them popular or unpopular, so to say. So let's go through those 10 frameworks. So I will make a comparison of those frameworks with the pros and cons and I will also briefly tell you about those frameworks so that everything falls together. So this is the outline of the module. So we will look at first the front end or the client side frameworks. And then we will look at the back end or the server side web development frameworks. If you recall that these frameworks facilitate in development of those wonderful web based database enabled websites, so let's go ahead. So pros and cons, so let's first talk about Django, okay, so you can see that it is the cons are it is monolithic. Monolithic means that it is kind of a one tier application. So it is kind of a bulky application. And since it is monolithic, so it is no wonder that it is not the fastest one. Okay, that is very clear. Now one thing which is very clear over here also is that it has great documentation. It has great documentation. And of course, there is something which is over here, which is security, it is secure. So if we are working in the context, say, e-commerce websites of which involves security, Django is the thing to go. Now there is something which you will be seeing over here, which is MVP MVP stands for minimum functionality product. And this is used to get the user feedback, user feedback. And this user feedback is then used to enhance that application. It is scalable and flexible. Now there are thousands of projects using Django, thousands, okay, thousands of projects using Django. And it's one of the older website development frameworks. It was released in 2005. In 2005, it's still one of the topics due to its modern view on problem solving and constant improvements, right? And it is developed using Python, which is one of the most used programming languages. So it is Python based. So let's look at the next one. So we have ExpressJS. Its simplicity is the main thing. Simplicity is the main thing. And web development framework, one of the many open source framework. It is also open source, source frameworks. And the string is that it's a great number of out-of-the-box tools. And many solutions can be made with just a couple of code of lines. So it is packages for API development that we have discussed in a lot of details. Now this is the problem over here. These error messages are not very helpful. So this is one of the cons. And this simplicity, as a matter of fact, becomes its weakness also. It is not suitable for heavy applications. So you see that there has to be balance over here. Then we have Ruby on Rails, which is written in the Ruby language. This is the language, Ruby language. Okay, and it is used today by more than, actually, it is around a million, around a million users, okay, live websites, such as Airbnb. Airbnb uses them, Airbnb uses them. Yellow pages, Groupon and many others. This web framework has a wide spectrum of users, including solving very complicated development problems, okay? But you see that it is very fine. It has many things over here. But because of this documentation issue over here, that is not good. That is a con over here, okay? So, and fast development at the same time, not a good choice for heavy loads, all right? So let's move on, and we have Spring. So Spring is the main purpose, the ability to simplify creation of J2J applications. Enterprise applications. It is possible, and it has many advantages, provide you with a framework for your future applications. It has strict architecture. It simplifies the process a lot, okay? Now, it is difficult to learn. It is wonderful. So if you recall when we were looking at some of the red applications, I mentioned that Java also has a steep learning curve, and this is thing over here also. And it can be unstable also, okay? And of course, it is known for its weekend dependency between objects and the absence of the necessity to connect objects manually. So connection is, manual connection is also a problem, manual connection, okay? In addition to its instability. So let's look at symphony. So it has fast development, good, okay? Reusable code, and you see that it has great documentation. So this great documentation was not the case for the prior, which we also discussed, okay? So its strength is stability, high speed, flexibility, okay? And possibility for code reuse, code reuse is there. And of course, when you look at high performing applications, it is a very convenient, even dispatcher together with dependency injection and possibilities for code optimization. Not only the code is used, but it can also be optimized. So these are some of the strengths of symphony, but of course, it is comparatively slow. So if you're looking at some fast applications, this is not the best choice. Now, let's look at some of the back end frameworks, pros and cons of the back end frameworks. So let's look at Angular. Usually it is considered the best, it is the best one, okay? And it is from the Google AngularJS, its predecessor, its predecessor was AngularJS, okay? And the first release in 2009, and it was then completely written in 2016. So you see that it is good for MVP in prototyping and easy to write the test also. But you see over here, again, quite difficult to learn. The learning curve is difficult, all right? And let's gain the issues of the documentation. CLI is the command line documentation, okay? And then we have the ember, okay? And after the ember, you see, again, difficult to learn. Again, difficult to learn. So these are the cons over here. And finally, we end with the React and ValueJS. You see, the problem over here is poor documentation. So you see that it is not the strength of this frameworks, but there are certain issues over here which are common across all of them. What are the issues? Issues are the documentation, the issues are the speed, and the issues are the learning curve, okay? So that's all I have for you in this module. Thank you very much.