title
What are Microservices | Microservices Architecture Training | Microservices Tutorial | Edureka

description
🔥 Microservices Architecture Training (Use Code "𝐘𝐎𝐔𝐓𝐔𝐁𝐄𝟐𝟎"): https://www.edureka.co/microservices-architecture-training This Edureka's Microservices video on What are Microservices gives you an introduction to microservices and also shows the practical implementation of microservices with a demo. In this video, you will learn the following: 1.Why Microservices 2.What Is Microservice Architecture 3.Features Of Microservice Architecture 4.Advantages Of Microservice Architecture 5.Companies Using Microservices 6.Hands-On Using SpringBoot #Microservices #MicroserviceArchitectureTutorial #MicroservicesForBeginners #MicroservicesOnlineTraining#MicroservicesWithSpringBoot How it Works? 1. This is a 4 Week Instructor-led Online Course. 2. We have a 24x7 One-on-One LIVE Technical Support to help you with any problems you might face or any clarifications you may require during the course. 3. At the end of the training, you will be working on a real-time project for which we will provide you a Grade and a Verifiable Certificate! --------------------------------------------------------------------------------- About Microservices Architecture Training Edureka’s Microservices Architecture training introduces you to the concept of Microservices that are small, lightweight, process-driven components. So, Microservices are the next important thing in designing scalable, easy-to-maintain applications. This not only makes application development easier but also offers great flexibility and lets you utilize various resources optimally. If you want to build an enterprise-ready implementation of the Microservices architecture, then this course is the first step for you! In this Microservices Architecture training, we will start by giving you a deep understanding of the core Microservices concepts and principle with insight in how they have evolved. We will walk you through the complete life cycle - from design to development to testing; including cross-layer concepts such as how to secure Microservices. ------------------------------------------------------------------------ What are the Objectives of our Microservices Architecture Training? After completing, Edureka's Microservice training, you will be able to: 1.Understand and differentiate between various Microservices Architectural styles 2.Apply Microservices Architecture principles 3.Know how to make the appropriate Microservice Architecture decision 4.Develop and test a Microservice 5.Know what technologies can be used to enable Microservices with an example --------------------------------------------------------------- Why should you go for Microservices Architecture Training? Microservices Architecture, or simply Microservices, is a unique method of developing software systems as a suite of independently deployable, small, modular services in which each service runs a unique process and communicates through a well-defined, lightweight mechanism to serve a business goal. Thanks to its scalability, this architectural method is considered ideal when you have to enable support for a range of platforms and devices spanning across the web, mobile, Internet of Things, and so on. Because of its flexibility, you can also use this method when you’re not sure what kind of devices you’ll need to support in an increasingly Cloud-based future. -------------------------------------------------------------------------------- What are the Pre-Requisites for Microservices Architecture Training ? There are no prerequisites for attending this Microservice course. Understanding of programming languages such as Java, basic understanding and familiarity with Spring Boot framework and building Java applications would be useful to execute Case Study and Project. ---------------------------------------------------------------------------------------------------- Who should go for this Microservices Architecture Training? 1.Application Architects 2.Software Architects 3.Application Developers 4.Developer working on Web, Cloud, Mobile, and other social technologies Facebook: https://www.facebook.com/edurekaIN/ Twitter: https://twitter.com/edurekain LinkedIn: https://www.linkedin.com/company/edureka For more information, please write back to us at sales@edureka.co or call us at IND: 9606058406 / US: 18338555775 (toll-free).

detail
{'title': 'What are Microservices | Microservices Architecture Training | Microservices Tutorial | Edureka', 'heatmap': [{'end': 659.654, 'start': 616.466, 'weight': 0.874}], 'summary': "Explores microservices architecture, discussing the drawbacks of monolithic architecture and defining microservices through a demo. it also covers the advantages and drawbacks of monolithic architecture in e-commerce, introduces microservices architecture, and discusses api gateway's role in handling requests for multiple services. additionally, it highlights microservices benefits and their implementation using spring boot and maven projects in an e-commerce simulation.", 'chapters': [{'end': 120.222, 'segs': [{'end': 62.657, 'src': 'embed', 'start': 34.286, 'weight': 0, 'content': [{'end': 39.287, 'text': 'there will be a demo based on microservices in which will have three services that will be communicating with each other.', 'start': 34.286, 'duration': 5.001}, {'end': 43.028, 'text': "So let's move forward guys and focus on why we need microservices.", 'start': 39.747, 'duration': 3.281}, {'end': 48.909, 'text': 'So before microservices we all know that there was an architectural pattern called monolithic architecture that was used.', 'start': 43.768, 'duration': 5.141}, {'end': 49.81, 'text': 'All right.', 'start': 49.45, 'duration': 0.36}, {'end': 52.11, 'text': 'so there are certain disadvantages of that architecture.', 'start': 49.81, 'duration': 2.3}, {'end': 55.631, 'text': 'but let me first explain you that architecture what exactly monolithic architecture means.', 'start': 52.11, 'duration': 3.521}, {'end': 62.657, 'text': 'So basically in this the entire software is composed in a single piece that is designed to be self-contained.', 'start': 56.374, 'duration': 6.283}], 'summary': 'Microservices demo with 3 services. discussing disadvantages of monolithic architecture.', 'duration': 28.371, 'max_score': 34.286, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N034286.jpg'}, {'end': 96.871, 'src': 'embed', 'start': 71.762, 'weight': 1, 'content': [{'end': 77.705, 'text': "I'll say that it will give you a tightly coupled software where each component, along with its associated components,", 'start': 71.762, 'duration': 5.943}, {'end': 80.666, 'text': 'must be present in order to execute or compile the code.', 'start': 77.705, 'duration': 2.961}, {'end': 83.668, 'text': 'So all of these components are actually dependent on each other.', 'start': 80.987, 'duration': 2.681}, {'end': 89.769, 'text': 'So if you notice a definition that is there in front of your screen, it says that monolithic architecture is like a big container.', 'start': 84.088, 'duration': 5.681}, {'end': 91.61, 'text': 'right, think of it as a big container.', 'start': 89.769, 'duration': 1.841}, {'end': 96.871, 'text': 'within all the software components of an application are assembled together and tightly packaged right?', 'start': 91.61, 'duration': 5.261}], 'summary': 'Monolithic architecture results in tightly coupled software components, all dependent on each other.', 'duration': 25.109, 'max_score': 71.762, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N071762.jpg'}], 'start': 4.741, 'title': 'Microservices architecture', 'summary': 'Delves into the necessity of microservices, drawbacks of monolithic architecture, and defines microservices through a demo displaying communication between three services.', 'chapters': [{'end': 120.222, 'start': 4.741, 'title': 'Understanding microservices architecture', 'summary': 'Discusses the need for microservices, the drawbacks of monolithic architecture, and the definition of microservices with a demo showcasing communication between three services.', 'duration': 115.481, 'highlights': ['Microservices offer loosely coupled architecture, reducing dependencies and allowing individual components to be independent. Microservices provide loosely coupled architecture, reducing dependencies and enabling individual components to be independent, enhancing flexibility and scalability.', 'Explanation of monolithic architecture, where all software components are tightly interconnected and interdependent. Detailed explanation of monolithic architecture, emphasizing the tight interconnection and interdependence of all software components, leading to drawbacks in flexibility and scalability.', 'Demo of microservices showcasing communication between three services, illustrating the practical implementation of microservices architecture. Demonstration of microservices with three services communicating, showcasing the practical implementation of microservices architecture and its benefits in real-world scenarios.']}], 'duration': 115.481, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N04741.jpg', 'highlights': ['Microservices offer loosely coupled architecture, reducing dependencies and allowing individual components to be independent, enhancing flexibility and scalability.', 'Detailed explanation of monolithic architecture, emphasizing the tight interconnection and interdependence of all software components, leading to drawbacks in flexibility and scalability.', 'Demonstration of microservices with three services communicating, showcasing the practical implementation of microservices architecture and its benefits in real-world scenarios.']}, {'end': 430.241, 'segs': [{'end': 187.443, 'src': 'embed', 'start': 160.093, 'weight': 0, 'content': [{'end': 165.359, 'text': 'so we have customer service, product service and card service, and when you deploy all these services,', 'start': 160.093, 'duration': 5.266}, {'end': 168.222, 'text': 'it will be basically a single monolithic application.', 'start': 165.359, 'duration': 2.863}, {'end': 170.818, 'text': 'Now what you can do is in order to scale it.', 'start': 168.817, 'duration': 2.001}, {'end': 174.059, 'text': 'you can run multiple instances of this application behind a load balancer.', 'start': 170.818, 'duration': 3.241}, {'end': 177.22, 'text': 'right now, let me discuss few advantages of this application.', 'start': 174.059, 'duration': 3.161}, {'end': 180.341, 'text': 'So, first of all, it is very, very simple to develop, right,', 'start': 177.26, 'duration': 3.081}, {'end': 184.742, 'text': 'as a goal of the development tools and IDs is to support the development of monolithic application.', 'start': 180.341, 'duration': 4.401}, {'end': 187.443, 'text': 'It makes the development really easy and one directional.', 'start': 184.842, 'duration': 2.601}], 'summary': 'Combining customer service, product service, and card service creates a simple, scalable monolithic application, easy to develop and scale.', 'duration': 27.35, 'max_score': 160.093, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N0160093.jpg'}, {'end': 223.773, 'src': 'embed', 'start': 194.025, 'weight': 1, 'content': [{'end': 196.086, 'text': 'that executable file can be a word file as well.', 'start': 194.025, 'duration': 2.061}, {'end': 200.763, 'text': 'Now, it is pretty simple to scale as well because you know in order to scale your application.', 'start': 196.641, 'duration': 4.122}, {'end': 204.405, 'text': 'All you have to do is run multiple copies of the application behind a load balancer.', 'start': 200.923, 'duration': 3.482}, {'end': 209.648, 'text': 'Now since everything comes with its pros and cons monolithic architecture also has few major drawbacks.', 'start': 204.925, 'duration': 4.723}, {'end': 211.609, 'text': "Let's discuss about them one by one.", 'start': 210.108, 'duration': 1.501}, {'end': 214.944, 'text': 'The first disadvantage is large and complex applications.', 'start': 212.481, 'duration': 2.463}, {'end': 219.409, 'text': 'Now, if you have a large application, or you can say, with the increase in size of the application,', 'start': 215.384, 'duration': 4.025}, {'end': 223.773, 'text': 'it becomes really complex to understand and modify such applications right and, as a result,', 'start': 219.409, 'duration': 4.364}], 'summary': 'Scaling is achieved by running multiple copies of the application behind a load balancer. monolithic architecture has drawbacks, including large and complex applications.', 'duration': 29.748, 'max_score': 194.025, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N0194025.jpg'}, {'end': 284.332, 'src': 'embed', 'start': 256.526, 'weight': 3, 'content': [{'end': 261.172, 'text': 'So the code base is pretty large because the entire application is one monolithic application right?', 'start': 256.526, 'duration': 4.646}, {'end': 262.895, 'text': 'There are not different different services present.', 'start': 261.212, 'duration': 1.683}, {'end': 265.027, 'text': 'Now it blocks continuous development.', 'start': 263.567, 'duration': 1.46}, {'end': 269.728, 'text': 'So what I mean by that a large monolithic application is an obstacle to frequent deployments.', 'start': 265.047, 'duration': 4.681}, {'end': 276.91, 'text': 'Let me tell you how in order to update one component you have to redeploy the entire application which interrupts the background task.', 'start': 269.769, 'duration': 7.141}, {'end': 284.332, 'text': 'So, if I have to take the example of the e-commerce website, if I have to update the card service, I have to redeploy the entire application,', 'start': 276.93, 'duration': 7.402}], 'summary': 'Large monolithic application impedes frequent deployments, requiring redeployment of entire application to update one component.', 'duration': 27.806, 'max_score': 256.526, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N0256526.jpg'}, {'end': 338.948, 'src': 'embed', 'start': 306.651, 'weight': 4, 'content': [{'end': 308.711, 'text': "I know I've told you that it's pretty easy to scale,", 'start': 306.651, 'duration': 2.06}, {'end': 313.993, 'text': 'but let me tell you what are the disadvantages when it comes to scalability and in terms of monolithic architecture.', 'start': 308.711, 'duration': 5.282}, {'end': 322.28, 'text': 'So each copy of application instance will get access to all the data right?, which makes caching less effective and increase memory consumption,', 'start': 314.453, 'duration': 7.827}, {'end': 323.643, 'text': 'along with input output traffic.', 'start': 322.28, 'duration': 1.363}, {'end': 328.099, 'text': 'Also, different application components have different resource requirements.', 'start': 324.196, 'duration': 3.903}, {'end': 333.804, 'text': 'one might be CPU intensive right, while other might be memory intensive and with the monolithic architecture.', 'start': 328.099, 'duration': 5.705}, {'end': 338.948, 'text': 'We cannot scale each component independently, right? So if you can see the example that is there in front of your screen.', 'start': 333.844, 'duration': 5.104}], 'summary': 'Scaling a monolithic architecture poses challenges: ineffective caching, increased memory consumption, and inability to scale components independently.', 'duration': 32.297, 'max_score': 306.651, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N0306651.jpg'}, {'end': 405.349, 'src': 'embed', 'start': 381.423, 'weight': 2, 'content': [{'end': 387.529, 'text': 'This makes the monolithic architecture highly unstable and unreliable the last and the final point is inflexible.', 'start': 381.423, 'duration': 6.106}, {'end': 393.535, 'text': 'So how is it inflexible guys with the monolithic architecture becomes really difficult to adopt new frameworks and languages.', 'start': 388.03, 'duration': 5.505}, {'end': 397.146, 'text': 'Suppose you have million lines of course written with XYZ framework.', 'start': 394.105, 'duration': 3.041}, {'end': 405.349, 'text': 'Now, it would be extremely expensive in terms of time, as well as cost, to rewrite the entire application, to use the newer ABC framework right?', 'start': 397.586, 'duration': 7.763}], 'summary': 'Monolithic architecture is unstable, unreliable, and inflexible, making it difficult and costly to adopt new frameworks and languages.', 'duration': 23.926, 'max_score': 381.423, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N0381423.jpg'}], 'start': 120.542, 'title': 'Monolithic architecture in e-commerce', 'summary': 'Explains the advantages and drawbacks of monolithic architecture in e-commerce, including its simplicity in development and deployment, ability to scale, and disadvantages such as complex development, hindrance to continuous deployment, scalability issues, unreliability, and inflexibility in adopting new technologies.', 'chapters': [{'end': 211.609, 'start': 120.542, 'title': 'Monolithic architecture in e-commerce', 'summary': 'Explains monolithic architecture using the example of an e-commerce website, discussing its advantages of simplicity in development and deployment, and the ability to scale by running multiple instances, while also highlighting its major drawbacks.', 'duration': 91.067, 'highlights': ['Monolithic architecture is a single instance application with common customer service, product service, and card service, easily scalable by running multiple instances behind a load balancer. The basic e-commerce application is deployed as a single monolithic application with common customer service, product service, and card service, which can be scaled by running multiple instances behind a load balancer.', 'Advantages of monolithic architecture include simplicity in development, deployment, and scaling. Monolithic architecture offers advantages such as simplicity in development, deployment, and scaling, making it very simple to develop and deploy, and easy to scale by running multiple copies behind a load balancer.', 'Monolithic architecture also has major drawbacks. While monolithic architecture has its advantages, it also has major drawbacks that need to be considered.']}, {'end': 430.241, 'start': 212.481, 'title': 'Disadvantages of monolithic architecture', 'summary': 'Outlines the disadvantages of monolithic architecture, including complex and slow development, hindrance to continuous deployment, scalability issues, unreliability, and inflexibility in adopting new technologies.', 'duration': 217.76, 'highlights': ['Monolithic architecture leads to large and complex applications, resulting in slow development and declining code quality over time. As the application size increases, it becomes complex to understand and modify, leading to slower development and declining code quality over time.', 'Large monolithic applications hinder frequent deployments and interrupt background tasks due to the need for redeployment of the entire application when updating a component. Large monolithic applications block continuous development as updating one component requires redeploying the entire application, leading to interruptions in background tasks and discouraging frequent updates.', 'Monolithic architecture leads to unscalability due to ineffective caching, increased memory consumption, and the inability to scale individual application components independently. Monolithic architecture leads to ineffective caching, increased memory consumption, and the inability to scale individual application components independently, posing challenges in scalability.', 'Tightly coupled components in monolithic architecture make the system unreliable, as a failure in one component can lead to the downfall of the entire application. Tightly coupled components in monolithic architecture make the system unreliable, as a failure in one component can lead to the downfall of the entire application, impacting its availability and stability.', 'Monolithic architecture poses inflexibility in adopting new frameworks and languages, as it becomes extremely expensive and time-consuming to rewrite the entire application for using newer technologies. Monolithic architecture poses inflexibility in adopting new frameworks and languages, as it becomes expensive and time-consuming to rewrite the entire application for using newer technologies, creating a significant barrier to adopting new technologies.']}], 'duration': 309.699, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N0120542.jpg', 'highlights': ['Monolithic architecture is a single instance application with common customer service, product service, and card service, easily scalable by running multiple instances behind a load balancer.', 'Advantages of monolithic architecture include simplicity in development, deployment, and scaling.', 'Monolithic architecture leads to large and complex applications, resulting in slow development and declining code quality over time.', 'Large monolithic applications hinder frequent deployments and interrupt background tasks due to the need for redeployment of the entire application when updating a component.', 'Monolithic architecture leads to unscalability due to ineffective caching, increased memory consumption, and the inability to scale individual application components independently.', 'Tightly coupled components in monolithic architecture make the system unreliable, as a failure in one component can lead to the downfall of the entire application.', 'Monolithic architecture poses inflexibility in adopting new frameworks and languages, as it becomes extremely expensive and time-consuming to rewrite the entire application for using newer technologies.']}, {'end': 652.914, 'segs': [{'end': 487.035, 'src': 'embed', 'start': 450.024, 'weight': 0, 'content': [{'end': 457.468, 'text': 'Now if I have to put it in simpler terms, basically, it is a self-contained process which avails different and unique business capabilities.', 'start': 450.024, 'duration': 7.444}, {'end': 463.269, 'text': 'Now, if you have large applications built using this architectural pattern, it can be broken down to small,', 'start': 457.928, 'duration': 5.341}, {'end': 468.571, 'text': "multiple services which together access one large system, but behind the scenes it's a microservice.", 'start': 463.269, 'duration': 5.302}, {'end': 473.832, 'text': "So what I'm trying to say here is we have multiple services on all of these services.", 'start': 469.011, 'duration': 4.821}, {'end': 478.113, 'text': "They don't share the data structure, but they'll be communicating through api's right.", 'start': 473.852, 'duration': 4.261}, {'end': 484.774, 'text': 'the major advantage of breaking down the system is now each microservice can focus on only one single business capability,', 'start': 478.113, 'duration': 6.661}, {'end': 487.035, 'text': 'which definitely leads to a better quality and throw.', 'start': 484.774, 'duration': 2.261}], 'summary': 'Microservices enable breaking down large applications into smaller, specialized services, enhancing the quality and efficiency of business capabilities.', 'duration': 37.011, 'max_score': 450.024, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N0450024.jpg'}, {'end': 541.33, 'src': 'embed', 'start': 502.621, 'weight': 2, 'content': [{'end': 509.987, 'text': 'all the components are divided into separate modules which communicate with each other using a well-defined interface, usually rest or messaging.', 'start': 502.621, 'duration': 7.366}, {'end': 521.996, 'text': 'now the communication between the microservices is a stateless communication where each pair of request and response is an independent transaction and because of this microservices can communicate effortlessly.', 'start': 509.987, 'duration': 12.009}, {'end': 524.226, 'text': 'Moreover in microservice architecture.', 'start': 522.486, 'duration': 1.74}, {'end': 525.827, 'text': 'The data is federated.', 'start': 524.246, 'duration': 1.581}, {'end': 527.647, 'text': 'All right, so let me just break it down for you.', 'start': 526.087, 'duration': 1.56}, {'end': 532.048, 'text': 'Each microservice is responsible for its own data model and data,', 'start': 528.207, 'duration': 3.841}, {'end': 537.449, 'text': 'because of which interaction with each microservice is handled by different instance and like in monolithic architecture,', 'start': 532.048, 'duration': 5.401}, {'end': 538.989, 'text': 'where we had only one instance here.', 'start': 537.449, 'duration': 1.54}, {'end': 541.33, 'text': 'We have multiple instances for different different microservices.', 'start': 539.009, 'duration': 2.321}], 'summary': 'Microservices communicate statelessly via well-defined interfaces, with federated data and multiple instances for different microservices.', 'duration': 38.709, 'max_score': 502.621, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N0502621.jpg'}, {'end': 616.446, 'src': 'embed', 'start': 587.023, 'weight': 4, 'content': [{'end': 588.804, 'text': 'where all of these services are running in one instance.', 'start': 587.023, 'duration': 1.781}, {'end': 590.045, 'text': "I hope you're getting my point.", 'start': 589.184, 'duration': 0.861}, {'end': 595.408, 'text': 'Now basically a team can update an existing service without rebuilding and deploying the entire application.', 'start': 590.525, 'duration': 4.883}, {'end': 599.69, 'text': "For example, if I have to update this particular service, I don't have to do it for the other services as well.", 'start': 595.428, 'duration': 4.262}, {'end': 602.212, 'text': 'I can just redeploy the service independently.', 'start': 600.051, 'duration': 2.161}, {'end': 607.738, 'text': 'Now, services are responsible for persisting their own data or external state internal implementation.', 'start': 602.634, 'duration': 5.104}, {'end': 611.121, 'text': 'details of each services are hidden from other services, moreover.', 'start': 607.738, 'duration': 3.383}, {'end': 616.446, 'text': "They don't need to share the same technology stack libraries or frameworks as well, right? You're getting my point.", 'start': 611.161, 'duration': 5.285}], 'summary': 'Services can be updated independently, without rebuilding the entire application, ensuring efficient and autonomous deployment.', 'duration': 29.423, 'max_score': 587.023, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N0587023.jpg'}], 'start': 430.281, 'title': 'Microservices architecture', 'summary': 'Introduces microservices architecture as an architectural style for breaking down large applications into small, autonomous services, enhancing quality and throughput. it also highlights key aspects such as stateless communication, independent data model, separate code base, and independent deployment.', 'chapters': [{'end': 502.621, 'start': 430.281, 'title': 'Microservices architecture', 'summary': 'Introduces microservices architecture, an architectural style that structures an application as a collection of small, autonomous services, enabling large applications to be broken down into multiple services, each focusing on a single business capability, leading to better quality and throughput.', 'duration': 72.34, 'highlights': ['Microservices architecture structures an application as a collection of small, autonomous services modeled around a business domain, enabling large applications to be broken down into small, multiple services.', 'Each microservice can focus on only one single business capability, leading to better quality and throughput.', "Microservices don't share the data structure but communicate through APIs, allowing for easier understanding and maintenance.", 'The example of an e-commerce site illustrates the difference between monolithic and microservices architecture.']}, {'end': 652.914, 'start': 502.621, 'title': 'Microservices architecture overview', 'summary': 'Highlights the key aspects of microservice architecture, emphasizing its stateless communication, independent data model for each microservice, separate code base for each service, and its independent deployment, while also discussing the management and service discovery components.', 'duration': 150.293, 'highlights': ['The communication between the microservices is stateless, enabling effortless communication, with each pair of request and response being an independent transaction.', 'Each microservice is responsible for its own data model and data, with multiple instances for different microservices, ensuring independent handling of interactions.', 'Services in microservice architecture are small, independent, and loosely coupled, with separate code bases managed by small development teams and deployed independently.', 'Updating an existing service in microservice architecture can be done without rebuilding and deploying the entire application, allowing independent redeployment.', 'Services are responsible for persisting their own data or external state, with internal implementation details hidden from other services, and they do not need to share the same technology stack, libraries, or frameworks.', 'Management components are responsible for placing services on nodes, identifying failures, and rebalancing services across nodes.', 'Service discovery component maintains a list of services and their locations on nodes, enabling service lookup to find the endpoint for a service.']}], 'duration': 222.633, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N0430281.jpg', 'highlights': ['Microservices architecture structures an application as a collection of small, autonomous services modeled around a business domain, enabling large applications to be broken down into small, multiple services.', 'Each microservice can focus on only one single business capability, leading to better quality and throughput.', 'The communication between the microservices is stateless, enabling effortless communication, with each pair of request and response being an independent transaction.', 'Each microservice is responsible for its own data model and data, with multiple instances for different microservices, ensuring independent handling of interactions.', 'Updating an existing service in microservice architecture can be done without rebuilding and deploying the entire application, allowing independent redeployment.']}, {'end': 858.161, 'segs': [{'end': 684.145, 'src': 'embed', 'start': 653.674, 'weight': 0, 'content': [{'end': 655.716, 'text': "Let's talk about API Gateway now.", 'start': 653.674, 'duration': 2.042}, {'end': 659.654, 'text': 'Right so API Gateway is basically the entry point for clients.', 'start': 656.272, 'duration': 3.382}, {'end': 664.356, 'text': "So this client won't call all these services directly right and first go to this API Gateway,", 'start': 660.094, 'duration': 4.262}, {'end': 669.118, 'text': 'which will forward the call to the appropriate services on the back end right?', 'start': 664.356, 'duration': 4.762}, {'end': 671.579, 'text': "If I'm a client, I'll request for this particular service,", 'start': 669.298, 'duration': 2.281}, {'end': 675.841, 'text': 'then I have to call the API Gateway and which will in turn call the service on the back end.', 'start': 671.579, 'duration': 4.262}, {'end': 681.404, 'text': 'Now the API Gateway might aggregate the responses from several services and return the aggregated response.', 'start': 676.221, 'duration': 5.183}, {'end': 684.145, 'text': 'Now, it might be possible right a client request for multiple services.', 'start': 681.424, 'duration': 2.721}], 'summary': 'Api gateway serves as entry point, aggregating responses from multiple services.', 'duration': 30.471, 'max_score': 653.674, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N0653674.jpg'}, {'end': 762.546, 'src': 'embed', 'start': 690.188, 'weight': 1, 'content': [{'end': 692.929, 'text': 'So I hope I am clear with the architecture.', 'start': 690.188, 'duration': 2.741}, {'end': 696.131, 'text': 'Let us focus on what are the features of microservices architecture.', 'start': 693.009, 'duration': 3.122}, {'end': 698.289, 'text': 'The first feature is small focused.', 'start': 696.727, 'duration': 1.562}, {'end': 699.45, 'text': 'So what it means?', 'start': 698.409, 'duration': 1.041}, {'end': 703.696, 'text': 'it means that the aim of microservice architecture is Simplicity, you know,', 'start': 699.45, 'duration': 4.246}, {'end': 709.202, 'text': 'so that it can be rewritten and maintained without any extra efforts by the development team.', 'start': 703.696, 'duration': 5.506}, {'end': 711.205, 'text': "right?. That's what I mean by small, focused.", 'start': 709.202, 'duration': 2.003}, {'end': 713.245, 'text': 'Then the next point is loosely coupled.', 'start': 711.744, 'duration': 1.501}, {'end': 720.109, 'text': "So as I've already mentioned multiple times that each micro service is independent of each other and do not need to coordinate as well.", 'start': 713.725, 'duration': 6.384}, {'end': 724.171, 'text': 'This makes the development, as well as the deployment, real quick, guys right?', 'start': 720.549, 'duration': 3.622}, {'end': 727.853, 'text': "So if I have to update a particular service, I'll only update that service.", 'start': 724.551, 'duration': 3.302}, {'end': 732.276, 'text': "I won't you know, update the other services right so that way deployment becomes really quick.", 'start': 727.893, 'duration': 4.383}, {'end': 734.137, 'text': "So that's the big advantage.", 'start': 732.616, 'duration': 1.521}, {'end': 735.938, 'text': "Now, let's talk about language neutral.", 'start': 734.157, 'duration': 1.781}, {'end': 739.019, 'text': 'So to be a good micro service, it must be language neutral.', 'start': 736.338, 'duration': 2.681}, {'end': 744.301, 'text': 'So what I mean by that for example in an application few services can be written in Python for fast deployment.', 'start': 739.039, 'duration': 5.262}, {'end': 749.842, 'text': "Whereas few might be written Java because it's speed and extensive libraries, right? So depends on the micro service.", 'start': 744.321, 'duration': 5.521}, {'end': 756.824, 'text': "What kind of programming language we are using so it doesn't really affect the other services right now bounded context.", 'start': 749.922, 'duration': 6.902}, {'end': 762.546, 'text': "So it means that each micro service doesn't need to understand the implementation of other microservice.", 'start': 757.024, 'duration': 5.522}], 'summary': 'Microservices architecture features: small focused, loosely coupled, language neutral, bounded context.', 'duration': 72.358, 'max_score': 690.188, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N0690188.jpg'}], 'start': 653.674, 'title': 'Api gateway and microservices architecture', 'summary': "Discusses api gateway's role as the entry point for clients, handling requests for multiple services and aggregating responses, and features of microservices architecture including small focused design, loose coupling, language neutrality, bounded context, independent development and deployment, fault isolation, mixed technology stack, and granular scaling, with examples of companies like amazon, netflix, soundcloud, twitter, uber, and paypal using microservices.", 'chapters': [{'end': 689.768, 'start': 653.674, 'title': 'Api gateway overview', 'summary': 'Discusses the role of api gateway as the entry point for clients, handling requests for multiple services and aggregating responses from various services before returning them to clients.', 'duration': 36.094, 'highlights': ['API Gateway serves as the entry point for clients, forwarding their requests to appropriate services on the backend.', 'It may aggregate responses from multiple services and return the aggregated response to the client.', "Clients' requests for multiple services can be handled by the API Gateway, which aggregates results from various services before returning the aggregated response."]}, {'end': 858.161, 'start': 690.188, 'title': 'Features of microservices architecture', 'summary': 'Discusses the features of microservices architecture, emphasizing small focused design, loose coupling, language neutrality, bounded context, and highlights the advantages including independent development and deployment, fault isolation, mixed technology stack, and granular scaling, with examples of companies like amazon, netflix, soundcloud, twitter, uber, and paypal using microservices.', 'duration': 167.973, 'highlights': ['Microservices architecture emphasizes small focused design, aiming for simplicity and easy maintenance without extra efforts by the development team.', 'Loosely coupled microservices enable independent development and deployment, making it real quick and advantageous for updating specific services without affecting others.', 'Language neutrality in microservices allows flexibility in using different programming languages for different services, such as Python for fast deployment and Java for speed and extensive libraries.', "Bounded context in microservices ensures that each microservice doesn't need to understand the implementation of other microservices, promoting independence and modularity.", 'Advantages of microservices architecture include independent development and deployment, fault isolation, mixed technology stack, and granular scaling, with examples of companies like Amazon, Netflix, SoundCloud, Twitter, Uber, and PayPal using microservices.']}], 'duration': 204.487, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N0653674.jpg', 'highlights': ['API Gateway serves as the entry point for clients, forwarding their requests to appropriate services on the backend.', 'Microservices architecture emphasizes small focused design, aiming for simplicity and easy maintenance without extra efforts by the development team.', 'Loosely coupled microservices enable independent development and deployment, making it real quick and advantageous for updating specific services without affecting others.', 'Language neutrality in microservices allows flexibility in using different programming languages for different services, such as Python for fast deployment and Java for speed and extensive libraries.', "Bounded context in microservices ensures that each microservice doesn't need to understand the implementation of other microservices, promoting independence and modularity."]}, {'end': 1218.54, 'segs': [{'end': 914.348, 'src': 'embed', 'start': 858.161, 'weight': 0, 'content': [{'end': 862.702, 'text': "because large applications become easier to manage when they're broken down into smaller composable pieces.", 'start': 858.161, 'duration': 4.541}, {'end': 864.962, 'text': "So, without any further delay, let's begin with.", 'start': 863.322, 'duration': 1.64}, {'end': 872.104, 'text': 'our hands-on will be using spring boot, because it provides a way to provide Java applications quickly and simply through an embedded server,', 'start': 864.962, 'duration': 7.142}, {'end': 874.344, 'text': 'and by default it is version of Tomcat.', 'start': 872.104, 'duration': 2.24}, {'end': 877.465, 'text': 'It will basically eliminate the need of Java double E containers.', 'start': 874.764, 'duration': 2.701}, {'end': 882.314, 'text': 'and with springboard we can expose components such as rest services independently,', 'start': 877.981, 'duration': 4.333}, {'end': 885.363, 'text': 'exactly as proposed in the microservice architecture that we have just discussed.', 'start': 882.314, 'duration': 3.049}, {'end': 887.452, 'text': 'in any maintenance of the components.', 'start': 885.831, 'duration': 1.621}, {'end': 891.553, 'text': 'We no longer make the redeploy of its consumers.', 'start': 887.872, 'duration': 3.681}, {'end': 893.354, 'text': "I'll tell you what exactly I mean.", 'start': 892.073, 'duration': 1.281}, {'end': 900.137, 'text': 'What is a consumer for this lab will use Eclipse oxygen and Maven 3 now to illustrate the concept of microservice.', 'start': 893.694, 'duration': 6.443}, {'end': 908.48, 'text': "What we'll do will create three Maven projects in this hands-on and each of them will symbolize back-end functionality or you can say reusable apis.", 'start': 900.197, 'duration': 8.283}, {'end': 912.105, 'text': 'and one of them held a composition fat to put it in simpler way.', 'start': 909, 'duration': 3.105}, {'end': 914.348, 'text': 'I will say it will be a consumer of the other two.', 'start': 912.145, 'duration': 2.203}], 'summary': 'Utilize spring boot to create microservices, eliminating need for java ee containers, and enabling independent component exposure and maintenance.', 'duration': 56.187, 'max_score': 858.161, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N0858161.jpg'}, {'end': 955.159, 'src': 'embed', 'start': 931.75, 'weight': 5, 'content': [{'end': 938.836, 'text': 'So this doctor microservice is the consumer right and consumer of the other two microservices that is patient and a diagnosis.', 'start': 931.75, 'duration': 7.086}, {'end': 941.225, 'text': 'All right, so that is how it is done.', 'start': 939.443, 'duration': 1.782}, {'end': 946.07, 'text': 'Now if I have to explain one of these services, let me explain you the patient microservice first.', 'start': 941.605, 'duration': 4.465}, {'end': 949.954, 'text': 'So over here as you can notice that we have a pom.xml file.', 'start': 946.55, 'duration': 3.404}, {'end': 955.159, 'text': 'So basically this pom.xml file will establish all the dependencies right before we start coding.', 'start': 950.354, 'duration': 4.805}], 'summary': 'Doctor microservice consumes patient and diagnosis microservices. patient microservice uses pom.xml for dependencies.', 'duration': 23.409, 'max_score': 931.75, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N0931750.jpg'}, {'end': 1087.421, 'src': 'embed', 'start': 1061.316, 'weight': 4, 'content': [{'end': 1067.498, 'text': 'And when I go to arguments, right, so I just have to write a minus D server dot port 8081.', 'start': 1061.316, 'duration': 6.182}, {'end': 1074.639, 'text': 'So you can see that my patient Microsoft will be running at a port 8081 when I started let me just start all these services one by one.', 'start': 1067.498, 'duration': 7.141}, {'end': 1076.54, 'text': "So I'll start this first.", 'start': 1075.02, 'duration': 1.52}, {'end': 1080.657, 'text': 'Just click on run as Spring Boot app.', 'start': 1078.055, 'duration': 2.602}, {'end': 1087.421, 'text': "Similarly, right click on this and I'll just run it as Spring Boot app again.", 'start': 1081.937, 'duration': 5.484}], 'summary': 'Starting services on port 8081 for microsoft patient system.', 'duration': 26.105, 'max_score': 1061.316, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N01061316.jpg'}], 'start': 858.161, 'title': 'Microservices benefits and implementation', 'summary': 'Covers the advantages of microservices, such as modularity and ease of deployment, and their implementation using spring boot for java applications and maven projects in an e-commerce simulation, showcasing the use of embedded servers and independent exposure of components as rest services.', 'chapters': [{'end': 893.354, 'start': 858.161, 'title': 'Microservices with spring boot', 'summary': 'Discusses the benefits of breaking down large applications into smaller composable pieces, and the use of spring boot for quickly and simply providing java applications with an embedded server, eliminating the need for java ee containers and allowing independent exposure of components as rest services in microservice architecture.', 'duration': 35.193, 'highlights': ['Spring Boot provides a way to provide Java applications quickly and simply through an embedded server, and by default, it is version of Tomcat.', 'With Spring Boot, we can expose components such as rest services independently, exactly as proposed in the microservice architecture.', 'Eliminates the need of Java EE containers and no longer requires the redeploy of its consumers.', "Large applications become easier to manage when they're broken down into smaller composable pieces."]}, {'end': 1218.54, 'start': 893.694, 'title': 'Microservices with maven and eclipse', 'summary': 'Illustrates the concept of microservices by creating three maven projects, symbolizing back-end functionality, with one being the consumer of the other two, running on different ports and simulating an e-commerce application.', 'duration': 324.846, 'highlights': ['Three Maven projects created to symbolize back-end functionality, with one being a consumer of the other two. Three Maven projects are created to represent back-end functionality, with one project serving as the consumer of the other two, demonstrating the concept of microservices.', 'Projects running on different ports, simulating an e-commerce application. The projects are configured to run on different ports, simulating an e-commerce application scenario, where one microservice is a consumer of the other two, akin to an order microservice being a consumer of product and customer microservices.', 'Explanation of patient microservice and its functionality. The patient microservice is explained, detailing the structure of the pom.xml file, common application files, and the purpose of patient.java and patient rest.java in providing input for variables.']}], 'duration': 360.379, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/gfWr2_H39N0/pics/gfWr2_H39N0858161.jpg', 'highlights': ['Spring Boot simplifies Java application deployment through an embedded server, eliminating the need for Java EE containers and redeployment of consumers.', 'Exposing components as rest services independently aligns with the microservice architecture, enhancing modularity and ease of management.', 'Breaking down large applications into smaller composable pieces with Spring Boot facilitates easier management.', 'Creation of three Maven projects to represent back-end functionality, with one project serving as the consumer of the other two, demonstrating the concept of microservices.', 'Configuring projects to run on different ports simulates an e-commerce application scenario, showcasing the interaction between microservices.', "Detailed explanation of the patient microservice's structure and functionality, including the pom.xml file, common application files, and the purpose of specific Java files."]}], 'highlights': ['Microservices offer loosely coupled architecture, reducing dependencies and allowing individual components to be independent, enhancing flexibility and scalability.', 'Monolithic architecture leads to large and complex applications, resulting in slow development and declining code quality over time.', 'Microservices architecture structures an application as a collection of small, autonomous services modeled around a business domain, enabling large applications to be broken down into small, multiple services.', 'API Gateway serves as the entry point for clients, forwarding their requests to appropriate services on the backend.', 'Spring Boot simplifies Java application deployment through an embedded server, eliminating the need for Java EE containers and redeployment of consumers.']}