Microservice Architecture | Microservices Tutorial | Microservices | Edureka Rewind

Key Takeaways

hey guys this is sahti from urea and today we will be learning about microservice architecture so before I start with the session let's take a look at today's agenda initially we will start talking about the previous system that was the monolithic architecture followed by its challenges then we'll jump on to the functionalities of microservices and the best practices to design them after going through all the concepts we will go through a real life use case of uber and understand them better so let's get started with the session what do you think monolithic architecture was well I could say that it was like a big container where all the software components of an application were tightly packed together have you got any idea how the applications on this framework worked how they looked like how they performed how they communicated with each other and so on let's look at the client server model shown here what do you see as a user as a user when you open a web UI you just see a website but behind the scenes the server side application has different features which have to be handled together features such as handling HTTP requests retrieving and updating the data from database and executing a domain specific logic were put on a single framework so if any one feature of this service side application had not worked then the complete system would go down also if only any one feature had to be updated then the complete system had to be built again now let's understand more about monolithic architecture by using a shopping cart application for reference as a user when you open a shopping cart application what all do you see you see different features for handling wish list new labels new brands in the markets customer services and so on but if the de velers of this framework had decided to build this application on a single framework then all the features were put together on a single database this not only created problem for scalability but also for fault tolerance and Agility let's understand these challenges one by one specifically the first challenge that we're going to talk about is agility let us consider an asset management industry here different clients come with different Investments who have to be offer different services so if any new Services had to be given to any new clients or any new changes had to be made do you think monolithic application could accommodate these changes well I would say it definitely could but yes there's a problem here the problem is here it could accommodate the changes but at the cost of reduced agility why do you think this happened this happened because even if a small component in an application had to be changed the entire application had to be repackaged together let's look at the Second Challenge consider yourself as a developer now so if you had built any application you would obviously want it to scale as per the future Trends but if you had built this application on a monolithic architecture how do you think you could keep up with the scalability well let's take an example our shopping cart application is built on a monolithic framework now consider three customers come on to the app application just to accommodate these three new customers three instances of the same application have to be created also apart from the three new instances of the application resources also get wasted for the services which need not have to be scaled let us now look into the third challenge which is fall tolerance consider your shopping cart application for reference suppose even if one feature of the application doesn't work then the entire system goes down this not not only creates a problem for the users but also creates a problem for the developers as they have to rebuild it again so to avoid these challenges developers of these applications decided to shift from monolithic architecture to microservices now many questions may come onto your mind such as what were the advantages of new architecture how could the developers benefit from the new architecture what were the new challenges that we faced with this architecture and so on let's discuss each of them one by one one let's start with what were microservices microservices are basically an architecture wherein a monolithic application is decomposed into small and micro applications which were packaged and deployed independently consider your shopping cart application for reference again imagine now that developers of this application have shifted its framework from a monolithic to a microservice architecture so this is how the architecture looks like now even now as a user when you open a shopping cart application you just see features put on together on a single website now there are separate teams handling different features that means there's a team of developer handling deal of the day a team of developers handling new labels a team of developer handling customer services and so on all teams now write codes for their features only making it easy to deploy individual features again and again whenever it is required how do you think these individual separation Deployable units communicate with each other well these separate individual Deployable units communicate with each other through a well-defined interface of rest or message bus by now you must have understood what were the functionalities of microservices and how they communicated with each other let's learn more about microservices by looking at different components of its architecture well the architecture starts with different clients from different devices trying to perform different management capability such as build search notification and so on then each and every functionality is segregated into separate microservices handling their own data for example microservice a could take care of search operation microservice B could take care of build operation micros service C could take care of notification feature and so on all these individual micros Services had their own load balancing and execution environments to perform different functionality and capture their own data these individual microservices then communicated within themselves through the rest or message bus to perform different operational capabilities such as Automation and monitoring also the requests of clients were passed on to the internal architecture through an API Gateway let's summarize the difference between both architectures before moving forward to the features of microservices and the use case so in short monolithic architecture had a single framework for all the features on a single database whereas microservice architecture had different microservices for each and every feature handling their own database now what features made the developers shift from a monolithic architecture to microservices let's have a look at them the applications built using microservice architecture were easily built altered and scaled they focused on a single capability all the components could be easily replaced the teams worked independently they allowed frequent releases of the software applications were treated as products there were no standardized patterns and most importantly all the features were quickly developed let's look into more of microservices and their implementation by using a real life use case of uber what do you know about Uber well Uber Technologies is a Global Taxi technology company headquartered in San Francisco United States operating in 633 cities worldwide like many other startups Uber also started its Journey with a monolithic architecture for a single City let's have a look at this architecture initially they had a rest API with which the passenger and the driver were connected this means that the mobile API was connected to the rest API which was then connected to the monolithic architecture as a backend server also for people accessing to web UI they were also connected to the same server coming forward there were three more adapters which were used to perform different functionalities such as notifications sending mails or messages billing payment Etc finally a mySQL database to capture all their data so if You observe here all the features such as passenger management billing notification features drip management driver management were composed in a single framework this means that having one code base seem clean at that time and solved Uber's Core Business problems which included connecting drivers with riders Billings and payments but as Uber started expanding worldwide into many more cities it continuously faced the problem of scalability and continuous integration so developers could not continuously build test deploy and release the software frequently as in when Uber started expanding city-wise throughout the world also adding new features and fixing bugs in a single repository became extremely difficult for the developers so to avoid such challenges Uber decided to follow the lead of hypergrowth companies like Amazon Netflix SoundCloud and Twitter and broke down its monolithic framework into multiple code bases to form a microservice architecture so this is how the new architecture looks like what do you think is the new change in the architecture well we could clearly see the introduction of API Gateway which connected all the drug drivers with the passengers also from the API Gateway all the internal points were connected such as passenger management drip management driver management and so on so basically anybody who connects to the API Gateway gets automatically connected to all the microservices another change that we observe in this architecture is the introduction of individual separate Deployable units here this means that we can deploy this unit or this unit or any other unit without disturbing the others let me explain you this point with an example consider yourself as one of the developers of uber so now if you want to change anything in the billing microservices then you just have to deploy only billing microservices and do not have to disturb the others also this kind of architecture helped Uber to scale its services individually let me explain you with an example as we all know the number of people searching for cabs are comparatively more than the number of people actually booking a cab and making payments so the number of processes working on the passenger management microservice are more than the number of processes working on the payments also it was observed that even if any one feature was D no other microservice would get affected therefore developers of uber need not build their applications again and again even if one microservice goes down now that you've seen a real life use case of uber can you think of any best practices to design microservices well let's have a look at them initially seate the data store for each micros service then keep the code at similar level of maturity now after this separately build each micros service according to its respective features and then deploy into containers lastly create the servers as stateless for communication now let me just give you a quick summary of what all we discussed list we started with the understanding of what was monolithic architecture and its challenges then we went through the microservice architecture and understood the differences between both the architectures after understanding the architectures we focused on the features of microservices and discuss the best practices to design them then we compared Uber's previous framework to the present one and understood what made them change their architecture thank you for watching this video and have a great day e e e e e e e e e e e e