Subtitles section Play video Print subtitles Welcome everyone to the session of Learn Design Pattern and architecture pattern step by step with the project And this complete series we are going to complete in flat 8 hours In 8 hours we will be completing most of the important patterns and architecture pattern in this project which we are going to just start The first question which will probably come to your mind is that Is it really possible to cover all the Design Pattern in 8 hours and that also in a single project that also with Architecture Pattern My answer is no In this project we will be covering almost 60% of the Gang of Four Design Pattern plus some other patterns which are other than gang of four As well as we will be covering at least 40-50% of the architecture patterns It is not possible to cover all the patterns in a project Because Design Patterns cannot be forcibly use in your project But I can tell you that in whatever project your are working at this moment at least 20-30% design patterns are already available Via this project my goal is to give you actual idea of how design pattern and architecture patterns are used in a project In case you are concerned saying that no I want to learn all the design patterns and that also I want to step by step You can follow our video series which have on Questpondvd.com Where we have explained 40-50 Design Patterns Which you can see here Factory pattern, Abstract Factory, Builder, Prototype Adapter, Decorator named that pattern It has been completed in this series There are two ways of learning Design Patterns One is if you are a person who wants to go concept by concept code by code here it is You can see that login to your questpondvd account see this sections step by step And the other way is by doing a project Take up a project start coding the design pattern and let fall naturally along the way If you are asking me the suggestions If you are asking me tell us what is good Is going code by code and pattern by pattern by pattern is good or the project based approach is good My personal choice is the project based approach Start with the project based approach but as i have told I can complete 60-70% Design Patter The remaining 30% are still left out Those 30% Design Pattern you can watch from here and second what I'll be doing when I am teaching you this project I will be telling you to go and see more about the Design Pattern in this section I'll be guiding you at right places to hop in this series and come back to this project My advice here would be to go via the project based approach and not via Design pattern after design approach I'll tell you why Design patterns are thought processes and thought processes cannot be explained via just sample code or PPTs or some UML diagrams If you see on the internet lot of people explain Design patterns by showing UML diagrams by showing examples like cars,trees and rivers which does not make any sense We need to do a real project We need to feel design pattern We need to understand it In what kind of scenario it has to be used The best way to learn design pattern is by doing a poject I would suggest you follow this video series and as time comes I will tell you to go and see the appropriate design pattern from this section here Before I move ahead Just talk about one myth which people have about design patterns Lot of people think that in order to do a good architecture or create a good architecture we need to implement all design patterns in our project Also I have seen that some of the developers try to force design patterns They say lets implement Factory pattern lets implement Singleton Pattern Bu the fact is Patterns come out naturally They are completely on demand as per the scenario It is a very horrible myth that you need to force design pattern or you need to implement design patterns for sibling your project or implement all design patterns in your project But the fact is that patterns are natural and tehy should come on demand Before we move ahead and we start defining design pattern we start looking at the project Let me spend 2 or 3 minutes here discussing about difference between design pattern architecture pattern and Architecture Style I have worked with so many developers across different geographical location with different culture But when it comes about differentiating between these three things People just use this words interchangeable This three things they must be looking very similar for you but they have a huge difference between them When you say design pattern Design pattern is actually at a code level When some says this is a factory Design Pattern He should actually show you some kind of a sood of .... He should should show you some kind of a logic When you say its a architecture pattern Its only block level diagrams For example Model View Controller is a architecture pattern Where we say there is a controller then there is a model There is a view The first hit comes to the controller and then it picks up the model and the view Over there we just draw block diagrams Its a 30000 feet level view of your project When we talk about architecture style they are just principles they are just one liner For example rest is a architecture style which follows HTTP protocol Design pattern it is at the code level at the sood of code level Somebody has to give you some kind of a sued a code then it becomes a design pattern Architecture pattern just overall blocks as I have said model view view model or UI layer and then model layer then data access layer These layers how they are implemented? What code goes into that? that is not we have shown here And architecture principles it is just principles just one liners