Microservices Tutorial for Beginners | Microservices Architecture | Microservices Training | Edureka

Key Takeaways

hi everyone first thing first we are going to talk about what exactly microservices are and then we will be taking it further in terms of our discussion on how we can work on those microservice deployments and how what is the main difference between microservice and the monolithic architecture that we have and how we can get started with those so that is what we are going to discuss so microservice is what microservice is basically dividing a monolithic architecture into smaller parts for example if you talk about the main application so it may be having for example let's suppose we have a client one for which we want to deploy the app we may have client fund for which we want to deploy the app so what we can do is we can go ahead and deploy all the components as a single entity for example here we can deploy let's say here we have the card system for this e-commerce application we have the payment system we have the catalog system we have the user management system we have a notification system and they all need to be up and running as a part of keeping the application up so if you want we can design all these Solutions we can deploy them all as a part of a single application package like we do in normal Docker so for example we can have a single Docker file created and that is going to run all of these components in a single container setup even if they are deployed in a cluster so again at the end each and every container is going to contain all the packages that means it is going to contain the shopping cart the payment system the catalog system everything all packaged inside a single container only that means if we have to update any of the existing packages then that is going to be not an easy task if we if any of the packages that means if suppose the payment system is not working then the entire application is going to go down because of f of one component since they are tightly coupled with each other so the application is go down it was going to go down and plus later on if we want to let's say update any one of the services then we have to always redeploy the entire package because here they are all packaged together so even a small change will require the entire app to be deploy again and again and if we are going to deploy the entire app again there is always a good possibility of making errors and those errors can make the entire application go down which is not going to be feasible for any company be it's for small to medium small medum or even for large scale Enterprises they are not going to be feasible these kind of frequent failes is so now this kind of setup where everything is packaged inside a given we can say application or a Contin so this kind of setup is what we refer as a part of Monolithic architecture so we can have a messaging system in place but again even though it is not going to work because here the entire setup is like a single package Al together so what we can do is now this is what we refer as a part of Monolithic architecture so we can conver conver this moric architecture into the micros service setup by com by splitting each and every part into smaller parts for example we have the catalog system so what we can do is we can Define for the catalog system as in we can Define catalog and we can Define catalog as a separate container we have a system for payment Gateway so payment can be deployed as a separate container separate package we have the shopping card so we have shopping card defined as a separate package separate card data so now instead of packaging everything inside single app we are Distributing them under different packages and if you want we can run multiple containers running the same service for example we can have three containers each for the payment systems for the shopping C for the user catalog system and so on so that even if one container is down still the load can be easily deploy handled by the containers deployed as a cluster we can do that second Advantage here is if we want to update a single package for example we looking to update only payment Gateway as suppose we have partnered with a new payment provider and now we are going to add that payment provider into our application so we don't have to touch the codes for shopping cart we don't have to touch the code for the user management the catalog system and everything we only have to touch the code for the pavment Gateway that's it and when we are going to update the pavment Gateway because it is being deployed as a part of multicluster setup so the load can be easy we can say handled by the other containers and once we have thly tested the entire vment then the load can be easily transferred from the main component to this as for the requirement so this is what we Define this is what we do by using a micros Service setup and microservices are and again they have been gaining popularity since 2015 only so majority of the applications now they are all divided into smaller components and that reduces the overall maintenance cost deployment cost for the companies so that the entire work can be minimized plus the avability of the application is also going to be increased because of the entire application now divided into separate core components so this is what we refer as as a part of microservice setup first of all clear out the concept of microservice before we see how they communicate to each other by using the messaging platform so that's how these all things are divided and there are multiple ways of creating the micros Service setup so first of all we have to make sure again the entire application should be working as an automated service so that we have list dependency of one component over the other the entire application should be highly scalable that means whenever you want to scale up or scale down the resources for any app we should be able to easily do that and then it should be completely decentralized so that we can work on managing the application at any point of time and again we can do that easily and then it should be resilient that means a fail failure of one node should not affect the availability of the application it should be easily replace with with whatever other noes we have so this is what is these are the core principles for any microservices and we have to make sure in case we have multiple container set up done then the entire load should be well distributed among different containers here so these all things should be well defined and that is what we do by using the multicontainer setup available here so these all components they also have to communicate to each other and they communicate via the messaging platform like we have we can make use of cavka we can make use of the online based messaging platform like for a we have sqs for the Su platform we can make use of the pubsub and the event Hub service and so on so these all are defined as a part of different platforms that we can use for managing the micros service application because at the end when we are going to refer to these they all have to communicate to each other so for example let's say if you take a simple example for MVC architecture the model is the one that gets the update model is the one that gets the that is going to be used for getting the database so view is what the users are going to see at the front end and then we have controller which simply adds like an intermediary between the database and the view so the users they are going to if they need a data they are going to send the request to controller the controller is then going to send the request to model to fetch the data and then model simply sends the data back to the controller and the controller is the one that gets the data and simply send this back to the view so that users they can get the new data set so here we are using an application server but again the main problem here is let's say if this particular we can say this backround server or this backend server is not available and still if the users they are continuously entering the fields for example they are continuously entering the form and again we there have 50 form submissions in every in a minute and suppose if there's no backend Ser server available for 5 minutes that means we will be processing we'll be losing those 150 form submission those 250 250 form submissions in 5 minutes that could be big loss for the company so we do need to have a messaging system put in place in between that can handle all the messages so whatever form fence or whatever messages are being generated by content they can be stored in this messaging platform like we have C we have inur we have the V have servers and then we can allow the other components to subscribe so whenever they are going to subscribe to the messages even though the front end is not available they can still read the data from from this topic and even though if the let's say if the backend not available they can still read the data from the topic here so again these things are all defined as a part of this set and this is where we are going to make use of the messaging platform in order to allow us to communicate these microservices components to each other so even they are going to send data and that both at a synchronous and asynchronous Manner and this is what we Define by using messaging platform here so let's talk about how these messaging platforms they all are going to be defined so there are multiple vendors out there who are giving us the access to this kind of messaging platform here so and if you talk about a then we do have a service called as event Hub and this microservice is widely used because there are multiple advantages for using this microservice we can say setup we we do get to make sure that the entire application can work independently and they are all going to communicate to each other by using the different apis so this is what we Define by using micros server let's see how we can set it up on top of the SEO platform so here we do have a service named as storage cues so we do have a storage account service in here we can in case we don't have a storage account available yet then we are going to create the storage account in case it is already available then we can go ahead and create the cues here so if you want we can start by creating a queue or we can make use of the service per setup so first of all once we have the queue created it is going to work just the way we have the sqs service offered by AWS which allows us to create a queue and that queue can be used for the used by the producers of the messages to generate the messages and going to save it there and then we can create multiple subscribers who are going to read those messages from the queue here let me check the access for the queue here just a minute everyone in the lab taking a bit of time everyone so no worries we'll be continuing on the same part in our subsequent session so again a big thank you to you all for being a part of the session everyone thank you for joining and have a great day head take care