title
Microservices vs SOA | Microservices Tutorial for Beginners | Microservices Training | Edureka

description
( Microservices Architecture Training: https://www.edureka.co/microservices-architecture-training ) This Edureka's video will help you understand what are microservices and their practical implementation using Spring Boot. In this video, you will learn the following: 1. Monolithic Architecture 2. Challenges Of Monolithic Architecture 3. What are Microservices 4. Microservice Architecture Components 5. Hands-On Using Spring Boot #Microservices #MicroserviceArchitectureTutorial #MicroservicesForBeginners #MicroservicesOnlineTraining #MicroservicesUsingSpringBoot --------------------------------------------------------------------------------- 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': 'Microservices vs SOA | Microservices Tutorial for Beginners | Microservices Training | Edureka', 'heatmap': [{'end': 185.041, 'start': 121.323, 'weight': 0.701}, {'end': 339.853, 'start': 302.08, 'weight': 0.849}, {'end': 527.94, 'start': 515.429, 'weight': 0.751}, {'end': 650.843, 'start': 625.154, 'weight': 0.711}], 'summary': 'Explains the differences between soa and microservices, highlighting challenges of monolithic applications and comparing service granularity, control, and interoperability. it also contrasts their usage in e-commerce, emphasizing benefits and suitability for different applications.', 'chapters': [{'end': 404.274, 'segs': [{'end': 104.582, 'src': 'embed', 'start': 76.749, 'weight': 1, 'content': [{'end': 82.152, 'text': 'They cannot be easily scaled and even if the application needs to be updated then the complete system has to be rebuilt.', 'start': 76.749, 'duration': 5.403}, {'end': 87.871, 'text': 'The next problem is that with these monolithic applications, they block continuous development.', 'start': 82.839, 'duration': 5.032}, {'end': 90.577, 'text': 'All the features cannot be built and deployed at the same time.', 'start': 88.051, 'duration': 2.526}, {'end': 92.261, 'text': 'They will have to be done separately.', 'start': 90.697, 'duration': 1.564}, {'end': 97.26, 'text': 'The next challenge with monolithic applications is that the development is very slow.', 'start': 92.879, 'duration': 4.381}, {'end': 104.582, 'text': 'They take a lot of time to be built, since each and every time, every feature has to be built one after the other, and, most of all,', 'start': 97.54, 'duration': 7.042}], 'summary': 'Monolithic applications hinder continuous development and slow down feature deployment.', 'duration': 27.833, 'max_score': 76.749, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/EpyPFnjue38/pics/EpyPFnjue3876749.jpg'}, {'end': 191.446, 'src': 'heatmap', 'start': 110.543, 'weight': 3, 'content': [{'end': 115.785, 'text': 'You are very limited and very constrained, right? So that is the challenge with monolithic applications.', 'start': 110.543, 'duration': 5.242}, {'end': 120.446, 'text': "So now let's go on to SOA, which is nothing but service-oriented architecture.", 'start': 116.605, 'duration': 3.841}, {'end': 124.345, 'text': 'Now with SOA these services or features.', 'start': 121.323, 'duration': 3.022}, {'end': 126.446, 'text': 'They are broken down right.', 'start': 124.805, 'duration': 1.641}, {'end': 129.568, 'text': 'the entire software application is not built as one,', 'start': 126.446, 'duration': 3.122}, {'end': 135.612, 'text': 'but the different features and the different services are broken down into smaller components right?', 'start': 129.568, 'duration': 6.044}, {'end': 139.174, 'text': "So that's why it's called course grained architecture and over here.", 'start': 135.632, 'duration': 3.542}, {'end': 147.099, 'text': "If we have, let's say, one software application inside which it provides, and if it provides like five features or four features,", 'start': 139.834, 'duration': 7.265}, {'end': 153.623, 'text': 'then all those are four features are delivered by four different services, and that is what you can see over here, right?', 'start': 147.099, 'duration': 6.524}, {'end': 159.026, 'text': 'There are four different services and each of these services would have multiple tasks inside them,', 'start': 153.643, 'duration': 5.383}, {'end': 167.371, 'text': 'and these smaller tasks are together delivered as one particular feature, and the whole software application comprises of a number of these features.', 'start': 159.026, 'duration': 8.345}, {'end': 171.632, 'text': "But with micro services, it's a little more different now.", 'start': 168.109, 'duration': 3.523}, {'end': 175.855, 'text': 'These features or services are further broken down into task level services.', 'start': 171.692, 'duration': 4.163}, {'end': 178.557, 'text': 'So here it was feature level services.', 'start': 176.355, 'duration': 2.202}, {'end': 185.041, 'text': 'Whereas the services here their task level each and every task in a particular feature.', 'start': 179.357, 'duration': 5.684}, {'end': 191.446, 'text': "that was broken down, and that's why you have multiple tasks and multiple services in a micro service architecture,", 'start': 185.041, 'duration': 6.405}], 'summary': 'Comparison of monolithic, soa, and microservices architectures in software development.', 'duration': 80.903, 'max_score': 110.543, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/EpyPFnjue38/pics/EpyPFnjue38110543.jpg'}, {'end': 200.229, 'src': 'embed', 'start': 168.109, 'weight': 4, 'content': [{'end': 171.632, 'text': "But with micro services, it's a little more different now.", 'start': 168.109, 'duration': 3.523}, {'end': 175.855, 'text': 'These features or services are further broken down into task level services.', 'start': 171.692, 'duration': 4.163}, {'end': 178.557, 'text': 'So here it was feature level services.', 'start': 176.355, 'duration': 2.202}, {'end': 185.041, 'text': 'Whereas the services here their task level each and every task in a particular feature.', 'start': 179.357, 'duration': 5.684}, {'end': 191.446, 'text': "that was broken down, and that's why you have multiple tasks and multiple services in a micro service architecture,", 'start': 185.041, 'duration': 6.405}, {'end': 194.268, 'text': 'and that is why this is called fine-grained architecture.', 'start': 191.446, 'duration': 2.822}, {'end': 200.229, 'text': 'So that is what the differences are between these three on a high level now before I go further and confuse you people.', 'start': 194.887, 'duration': 5.342}], 'summary': 'Micro services allow fine-grained task-level services, differing from feature-level services.', 'duration': 32.12, 'max_score': 168.109, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/EpyPFnjue38/pics/EpyPFnjue38168109.jpg'}, {'end': 339.853, 'src': 'heatmap', 'start': 264.883, 'weight': 0, 'content': [{'end': 272.966, 'text': 'So let me go forward and talk about the difference between these two which is nothing but microservice and SOA with respect to certain parameters.', 'start': 264.883, 'duration': 8.083}, {'end': 277.369, 'text': "Let's look at the difference between them with respect to architecture and coordination.", 'start': 273.746, 'duration': 3.623}, {'end': 284.275, 'text': 'So first of all in SOA, there are four different types of services first is business service.', 'start': 277.93, 'duration': 6.345}, {'end': 285.716, 'text': 'The next is Enterprise service.', 'start': 284.535, 'duration': 1.181}, {'end': 289.82, 'text': 'Then we have application service and then we have infrastructure service.', 'start': 286.157, 'duration': 3.663}, {'end': 297.086, 'text': 'So these four service types together form your SOA and they together deliver your software application.', 'start': 290.481, 'duration': 6.605}, {'end': 301.33, 'text': "Now, what are these different services and what do they do? Let's see that.", 'start': 297.907, 'duration': 3.423}, {'end': 303.761, 'text': 'First is business service, right?', 'start': 302.08, 'duration': 1.681}, {'end': 310.522, 'text': "So your business service is the one that's going to be performing your core business operations,", 'start': 304.281, 'duration': 6.241}, {'end': 316.724, 'text': 'and it can be either represented by your XML or by web service definition language.', 'start': 310.522, 'duration': 6.202}, {'end': 324.826, 'text': 'and then we have Enterprise Service, the Enterprise Services, that service which implements the functionality defined by your business service,', 'start': 316.724, 'duration': 8.102}, {'end': 330.448, 'text': 'and the Enterprise Service does it with the help of the application service and the infrastructure service.', 'start': 324.826, 'duration': 5.622}, {'end': 331.028, 'text': 'now moving on.', 'start': 330.448, 'duration': 0.58}, {'end': 333.371, 'text': 'We have application service.', 'start': 331.77, 'duration': 1.601}, {'end': 339.853, 'text': 'the application service is the actual core application or the core functionality of that feature,', 'start': 333.371, 'duration': 6.482}], 'summary': 'Comparison of microservice and soa with respect to architecture and coordination.', 'duration': 45.639, 'max_score': 264.883, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/EpyPFnjue38/pics/EpyPFnjue38264883.jpg'}, {'end': 374.49, 'src': 'embed', 'start': 348.115, 'weight': 6, 'content': [{'end': 357.238, 'text': 'the infrastructure service refers to those non-business or those non-technical operations such as auditing, scaling or security and all these things.', 'start': 348.115, 'duration': 9.123}, {'end': 364.726, 'text': 'Those are the different services in a SOA, but in case of microservices architecture, you do not have these many types of services.', 'start': 358.044, 'duration': 6.682}, {'end': 368.548, 'text': 'You just have a functional service and you have a infrastructure service.', 'start': 364.746, 'duration': 3.802}, {'end': 374.49, 'text': 'The functional service is basically the combination of a business service and Enterprise service and an application service.', 'start': 368.968, 'duration': 5.522}], 'summary': 'Microservices architecture simplifies services to functional and infrastructure services, unlike soa.', 'duration': 26.375, 'max_score': 348.115, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/EpyPFnjue38/pics/EpyPFnjue38348115.jpg'}], 'start': 5.31, 'title': 'Differences between soa and microservices', 'summary': 'Discusses challenges of monolithic applications and compares them with the benefits of soa and microservices, highlighting differences in service granularity and control, with soa being course-grained and centrally governed, while microservices are fine-grained and decentralized. it also explains the difference between microservices and soa, highlighting the types of services each architecture consists of.', 'chapters': [{'end': 110.483, 'start': 5.31, 'title': 'Soa vs microservices', 'summary': 'Explores the challenges of monolithic applications, highlighting their inflexibility, unreliability, and slow development, while comparing them with the benefits of service-oriented architecture (soa) and microservices.', 'duration': 105.173, 'highlights': ['Monolithic applications are inflexible, unreliable, and slow to develop, hindering scalability and continuous development.', 'Monolithic applications block continuous development and are not fit for complex architecture due to the inability to use different technologies.', 'Monolithic applications require the complete system to be rebuilt for updates, and are unable to easily scale.', 'Monolithic applications host a number of software components together, posing challenges in terms of flexibility, reliability, and scalability.', 'SOA and microservices offer flexibility, scalability, and the ability to use different technologies, enabling continuous development and better fit for complex architecture.']}, {'end': 264.343, 'start': 110.543, 'title': 'Comparison of monolithic, soa, and microservices', 'summary': 'Compares monolithic, service-oriented architecture (soa), and microservices, highlighting how soa and microservices differ in terms of service granularity and control, with soa being course-grained and centrally governed, while microservices are fine-grained and decentralized.', 'duration': 153.8, 'highlights': ['SOA is course-grained architecture where different services and features are broken down into smaller components, with multiple tasks delivered as one feature. SOA involves breaking down services and features into smaller components, delivering multiple tasks as one feature.', 'Microservices are fine-grained architecture where features or services are further broken down into task-level services, with multiple tasks and services in a microservice architecture. Microservices further break down features into task-level services, resulting in multiple tasks and services in the architecture.', 'SOA is like an orchestra with multiple services controlled by one director, working together in a centrally governed architecture. SOA is akin to an orchestra with services controlled by one director, working together in a centrally governed architecture.', 'Microservices have independent performers not controlled by one director, working separately in a decentralized governing architecture. Microservices have independent performers working separately in a decentralized governing architecture, without a central director.']}, {'end': 404.274, 'start': 264.883, 'title': 'Microservices vs soa', 'summary': 'Explains the difference between microservices and soa, highlighting that soa consists of four types of services (business, enterprise, application, infrastructure) while microservices architecture only has functional and infrastructure services.', 'duration': 139.391, 'highlights': ['SOA consists of four types of services: business, enterprise, application, and infrastructure, delivering software applications together.', 'Microservices architecture only has functional and infrastructure services, with functional service combining business, enterprise, and application services.', 'Business service in SOA performs core business operations and can be represented by XML or web service definition language.', 'Enterprise service in SOA implements the functionality defined by the business service, with the help of application and infrastructure services.', 'Application service in SOA is the core application functionality and can be invoked directly or through a user interface.', 'Infrastructure service in SOA refers to non-business or non-technical operations such as auditing, scaling, and security.']}], 'duration': 398.964, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/EpyPFnjue38/pics/EpyPFnjue385310.jpg', 'highlights': ['SOA and microservices offer flexibility, scalability, and the ability to use different technologies, enabling continuous development and better fit for complex architecture.', 'Monolithic applications are inflexible, unreliable, and slow to develop, hindering scalability and continuous development.', 'Monolithic applications require the complete system to be rebuilt for updates, and are unable to easily scale.', 'SOA is course-grained architecture where different services and features are broken down into smaller components, with multiple tasks delivered as one feature.', 'Microservices are fine-grained architecture where features or services are further broken down into task-level services, with multiple tasks and services in a microservice architecture.', 'SOA consists of four types of services: business, enterprise, application, and infrastructure, delivering software applications together.', 'Microservices architecture only has functional and infrastructure services, with functional service combining business, enterprise, and application services.']}, {'end': 718.074, 'segs': [{'end': 465.561, 'src': 'embed', 'start': 438.544, 'weight': 0, 'content': [{'end': 443.892, 'text': 'and if you want the different services to communicate with one another, then you would have to bring a particular platform right?', 'start': 438.544, 'duration': 5.348}, {'end': 446.456, 'text': "So that's where you have this messaging middleware.", 'start': 444.212, 'duration': 2.244}, {'end': 450.715, 'text': 'So, in case of SOA, there is something called as a messaging middleware,', 'start': 447.193, 'duration': 3.522}, {'end': 456.917, 'text': 'which acts as the communication point or the interaction point between the different applications which are in a different language.', 'start': 450.715, 'duration': 6.202}, {'end': 462.96, 'text': 'So you can see that this application is on either C sharp or dotnet, and this is on elastic Java beans right?', 'start': 456.977, 'duration': 5.983}, {'end': 465.561, 'text': "Similarly, here it's C plus plus and here it's Java.", 'start': 462.98, 'duration': 2.581}], 'summary': 'Messaging middleware facilitates communication between applications in different languages in soa.', 'duration': 27.017, 'max_score': 438.544, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/EpyPFnjue38/pics/EpyPFnjue38438544.jpg'}, {'end': 527.94, 'src': 'embed', 'start': 495.306, 'weight': 1, 'content': [{'end': 498.467, 'text': 'There is a direct communication between these two services and similarly,', 'start': 495.306, 'duration': 3.161}, {'end': 502.808, 'text': 'if you have another Java application which wants to communicate with another Java application,', 'start': 498.467, 'duration': 4.341}, {'end': 507.228, 'text': 'the communication would take place with the help of rest API and similarly, Java to C,', 'start': 502.808, 'duration': 4.42}, {'end': 510.389, 'text': 'sharp or dotnet would again take place with the help of a rest API.', 'start': 507.228, 'duration': 3.161}, {'end': 514.909, 'text': 'So there is no broker here or middleman, which is a messaging middleware.', 'start': 510.809, 'duration': 4.1}, {'end': 520.471, 'text': 'The communication is directly to the other application then comes service granularity.', 'start': 515.429, 'duration': 5.042}, {'end': 527.94, 'text': 'If you can remember, I earlier told that in micro services you do not have the software delivered as a whole.', 'start': 521.457, 'duration': 6.483}], 'summary': 'Direct communication between java applications using rest api, without a middleman or messaging middleware, in microservices architecture.', 'duration': 32.634, 'max_score': 495.306, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/EpyPFnjue38/pics/EpyPFnjue38495306.jpg'}, {'end': 540.564, 'src': 'heatmap', 'start': 515.429, 'weight': 0.751, 'content': [{'end': 520.471, 'text': 'The communication is directly to the other application then comes service granularity.', 'start': 515.429, 'duration': 5.042}, {'end': 527.94, 'text': 'If you can remember, I earlier told that in micro services you do not have the software delivered as a whole.', 'start': 521.457, 'duration': 6.483}, {'end': 530.661, 'text': 'right?. It is broken down into smaller features.', 'start': 527.94, 'duration': 2.721}, {'end': 537.463, 'text': 'And if you are basically performing an operation which involves multiple applications or multiple services,', 'start': 530.961, 'duration': 6.502}, {'end': 540.564, 'text': "then those services are called by one another when it's needed.", 'start': 537.463, 'duration': 3.101}], 'summary': 'Microservices architecture breaks down software into smaller features, allowing for direct communication between applications and services when needed.', 'duration': 25.135, 'max_score': 515.429, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/EpyPFnjue38/pics/EpyPFnjue38515429.jpg'}, {'end': 594.63, 'src': 'embed', 'start': 566.974, 'weight': 3, 'content': [{'end': 571.797, 'text': 'Now the catch here is each and every service request and service response takes 100 milliseconds.', 'start': 566.974, 'duration': 4.823}, {'end': 577.02, 'text': "Okay So let's assume it takes this much time the API calls and this is in case of micro services.", 'start': 572.017, 'duration': 5.003}, {'end': 584.544, 'text': 'So in the micro service architecture when each call takes 100 milliseconds in total for this service to get successfully return.', 'start': 577.6, 'duration': 6.944}, {'end': 586.025, 'text': 'It would take 600 milliseconds.', 'start': 584.644, 'duration': 1.381}, {'end': 594.63, 'text': "Now, that's an awful lot of time for an API call to complete successfully right for an API call to be made successfully and to be returned.", 'start': 586.505, 'duration': 8.125}], 'summary': 'In micro service architecture, each api call takes 100 milliseconds, totaling 600 milliseconds for a successful return.', 'duration': 27.656, 'max_score': 566.974, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/EpyPFnjue38/pics/EpyPFnjue38566974.jpg'}, {'end': 665.46, 'src': 'heatmap', 'start': 625.154, 'weight': 4, 'content': [{'end': 629.216, 'text': 'because all the three requests and responses would be made simultaneously.', 'start': 625.154, 'duration': 4.062}, {'end': 632.278, 'text': 'So you would be saving a good 400 milliseconds over here.', 'start': 629.717, 'duration': 2.561}, {'end': 636.981, 'text': 'So that is the difference in service granularity between SOA and micro services.', 'start': 632.658, 'duration': 4.323}, {'end': 641.063, 'text': 'So the next difference we are going to see is with respect to component sharing.', 'start': 637.481, 'duration': 3.582}, {'end': 644.317, 'text': 'This is very similar to the previous slide, again right,', 'start': 641.795, 'duration': 2.522}, {'end': 650.843, 'text': 'because then it would be the same order service which would be interacting with your different smaller applications,', 'start': 644.317, 'duration': 6.526}, {'end': 658.19, 'text': 'each for customer management and for warehouse management and for order fulfillment, and the data again would be stored in different databases.', 'start': 650.843, 'duration': 7.347}, {'end': 665.46, 'text': 'But there again is the difference in micro services because in the micro services architecture for each and every application.', 'start': 658.815, 'duration': 6.645}], 'summary': 'Switching to microservices can save 400 milliseconds, indicating a difference in service granularity compared to soa.', 'duration': 40.306, 'max_score': 625.154, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/EpyPFnjue38/pics/EpyPFnjue38625154.jpg'}, {'end': 725.004, 'src': 'embed', 'start': 699.448, 'weight': 2, 'content': [{'end': 706.954, 'text': 'right, your SOA uses middleware for communication and your micro services uses an API layer for communication.', 'start': 699.448, 'duration': 7.506}, {'end': 711.157, 'text': 'So that is about the differences between SOA and micro services.', 'start': 707.834, 'duration': 3.323}, {'end': 718.074, 'text': "Now, let's go ahead and look at the differences between the two by understanding with an example of a shopping cart.", 'start': 712.009, 'duration': 6.065}, {'end': 725.004, 'text': 'So every e-commerce portal will have a shopping cart right where you can add your products to the cart and then you can check out later.', 'start': 718.8, 'duration': 6.204}], 'summary': 'Soa uses middleware, microservices use api layer. contrasted using shopping cart example.', 'duration': 25.556, 'max_score': 699.448, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/EpyPFnjue38/pics/EpyPFnjue38699448.jpg'}], 'start': 404.795, 'title': 'Soa and microservices differences', 'summary': 'Discusses the heterogeneous interoperability between soa and microservices, emphasizing messaging middleware in soa and direct communication through rest apis in microservices. it also compares service granularity, highlighting the difference in response time and component sharing, with microservices taking 600 milliseconds for three service requests and having separate application-specific services and databases.', 'chapters': [{'end': 510.389, 'start': 404.795, 'title': 'Heterogeneous interoperability in soa and microservices', 'summary': 'Discusses the differences between soa and microservices in terms of heterogeneous interoperability, highlighting the use of messaging middleware in soa and direct communication through rest apis in microservices, enabling diverse applications to interact seamlessly.', 'duration': 105.594, 'highlights': ['SOA utilizes messaging middleware as the communication point between applications developed in different languages, facilitating interaction between diverse applications.', 'Microservices enable direct communication between applications of different languages and structures through REST APIs, ensuring seamless interaction.', 'The chapter emphasizes the use of messaging middleware in SOA and the absence of a broker in microservices, highlighting the contrast in communication approaches.']}, {'end': 718.074, 'start': 510.809, 'title': 'Service granularity and component sharing in soa vs microservices', 'summary': 'Compares the service granularity, highlighting that in microservices each call takes 100 milliseconds, resulting in a total of 600 milliseconds, whereas in soa, all three service requests and responses are made simultaneously, saving around 400 milliseconds. it also discusses the difference in component sharing, emphasizing that in microservices, each application has its own separate order service and database, unlike in soa.', 'duration': 207.265, 'highlights': ['The chapter compares the service granularity, highlighting that in microservices each call takes 100 milliseconds, resulting in a total of 600 milliseconds.', 'In SOA, all three service requests and responses are made simultaneously, saving around 400 milliseconds.', 'In microservices, each application has its own separate order service and database, unlike in SOA.']}], 'duration': 313.279, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/EpyPFnjue38/pics/EpyPFnjue38404795.jpg', 'highlights': ['SOA utilizes messaging middleware for diverse language interaction.', 'Microservices enable direct communication through REST APIs.', 'Comparison: SOA emphasizes messaging middleware, while microservices lack a broker.', 'Microservices: Each call takes 100ms, totaling 600ms for three requests.', 'SOA: Simultaneous requests and responses save around 400ms.', 'Microservices have separate application-specific services and databases.']}, {'end': 1119.1, 'segs': [{'end': 818.738, 'src': 'embed', 'start': 777.063, 'weight': 0, 'content': [{'end': 780.964, 'text': 'similarly, if you talk about a product catalog, you have other tasks right?', 'start': 777.063, 'duration': 3.901}, {'end': 788.586, 'text': 'So all these tasks together form one particular application service in case of a survey shopping application.', 'start': 781.484, 'duration': 7.102}, {'end': 798.61, 'text': 'But in case of micro services shopping application, each of the different tasks that these services provide, those tasks are broken down into smaller,', 'start': 789.204, 'duration': 9.406}, {'end': 799.57, 'text': 'fine-grained services.', 'start': 798.61, 'duration': 0.96}, {'end': 803.933, 'text': 'So here we have a feature level services where shopping cart is one feature,', 'start': 800.13, 'duration': 3.803}, {'end': 807.835, 'text': 'product catalog is one feature and user account application is one more feature.', 'start': 803.933, 'duration': 3.902}, {'end': 812.296, 'text': 'But in case of micro services, we have a separate billing service for shipping.', 'start': 808.235, 'duration': 4.061}, {'end': 814.197, 'text': 'We have a shipping options service.', 'start': 812.476, 'duration': 1.721}, {'end': 816.257, 'text': 'We have a tax calculation service right?', 'start': 814.277, 'duration': 1.98}, {'end': 818.738, 'text': 'So the different tasks in this particular feature.', 'start': 816.277, 'duration': 2.461}], 'summary': 'Comparing application services to microservices, featuring separate services for billing, shipping, and tax calculation.', 'duration': 41.675, 'max_score': 777.063, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/EpyPFnjue38/pics/EpyPFnjue38777063.jpg'}, {'end': 878.185, 'src': 'embed', 'start': 854.309, 'weight': 2, 'content': [{'end': 862.655, 'text': "So here we'll have certain features which are common to multiple applications, right? So we have something like a display image server.", 'start': 854.309, 'duration': 8.346}, {'end': 870.12, 'text': "So it's a smaller task level servers over here, but the image of the product of being displayed might be common across all the three applications.", 'start': 862.675, 'duration': 7.445}, {'end': 878.185, 'text': 'It might be present in the shopping cart also, and the image of the product might be present in the user account application also,', 'start': 870.78, 'duration': 7.405}], 'summary': 'Common image server for multiple applications to display product images.', 'duration': 23.876, 'max_score': 854.309, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/EpyPFnjue38/pics/EpyPFnjue38854309.jpg'}, {'end': 1027.593, 'src': 'embed', 'start': 996.18, 'weight': 4, 'content': [{'end': 999.762, 'text': 'but then there are also times when an SOS shopping application is better for you.', 'start': 996.18, 'duration': 3.582}, {'end': 1005.025, 'text': 'So this was a classic use case of where a micro service shopping application is a best fit.', 'start': 1000.022, 'duration': 5.003}, {'end': 1012.781, 'text': "But let's see a use case where an SOA type of a shopping application and the SOA architecture comes out better,", 'start': 1005.675, 'duration': 7.106}, {'end': 1016.644, 'text': 'and that example is when your product is not actually that big.', 'start': 1012.781, 'duration': 3.863}, {'end': 1019.947, 'text': 'So in this case, yeah, you have a lot of functionalities.', 'start': 1017.024, 'duration': 2.923}, {'end': 1021.788, 'text': 'You have a lot of features and tasks.', 'start': 1019.967, 'duration': 1.821}, {'end': 1027.593, 'text': 'So just consider the example of a very simple software application, which needs three primary functionalities.', 'start': 1022.589, 'duration': 5.004}], 'summary': 'Microservice shopping app is best for complex products, soa suits smaller ones.', 'duration': 31.413, 'max_score': 996.18, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/EpyPFnjue38/pics/EpyPFnjue38996180.jpg'}, {'end': 1085.08, 'src': 'embed', 'start': 1051.269, 'weight': 3, 'content': [{'end': 1058.033, 'text': "If you're having, if you're implementing microservices architecture, then you will have to go through a lot of trouble, which can simply be avoided,", 'start': 1051.269, 'duration': 6.764}, {'end': 1060.555, 'text': 'because your application is in itself very simple.', 'start': 1058.033, 'duration': 2.522}, {'end': 1062.116, 'text': 'You have to just, You know,', 'start': 1060.575, 'duration': 1.541}, {'end': 1068.962, 'text': 'create one one website where you can have one website in which you have a cart where and you can add your products which you want to buy.', 'start': 1062.116, 'duration': 6.846}, {'end': 1069.863, 'text': "then, when you're checking out,", 'start': 1068.962, 'duration': 0.901}, {'end': 1075.007, 'text': 'you can have the user information displayed and then you have details about the product with this separate application.', 'start': 1069.863, 'duration': 5.144}, {'end': 1077.889, 'text': 'So in this case, it could just be these three different services.', 'start': 1075.487, 'duration': 2.402}, {'end': 1079.811, 'text': 'So that is a different between an SOA.', 'start': 1078.35, 'duration': 1.461}, {'end': 1085.08, 'text': 'So I think by now you understand that neither of them is better than the other, right?', 'start': 1080.538, 'duration': 4.542}], 'summary': 'Implementing microservices architecture can be avoided for a simple application, with just three different services.', 'duration': 33.811, 'max_score': 1051.269, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/EpyPFnjue38/pics/EpyPFnjue381051269.jpg'}], 'start': 718.8, 'title': 'Microservices and soa in e-commerce', 'summary': 'Discusses the concept of microservices in e-commerce, outlining the breakdown of tasks and features into smaller, fine-grained services and highlighting the benefits of this approach. it also contrasts microservices with soa shopping applications, emphasizing advantages and suitability for different types of applications.', 'chapters': [{'end': 888.032, 'start': 718.8, 'title': 'Microservices in e-commerce', 'summary': 'Discusses the concept of microservices in e-commerce, outlining the breakdown of tasks and features into smaller, fine-grained services, and highlighting the benefits of this approach in improving application modularity and reusability.', 'duration': 169.232, 'highlights': ['Microservices involve breaking down feature-level services into task-level services, such as separate billing and shipping options services in the shopping application. Microservices involve breaking down feature-level services into task-level services, such as separate billing and shipping options services in the shopping application.', 'The concept of microservices in e-commerce results in smaller, fine-grained services, such as display product service, update display service, and user default service in the product catalog application. The concept of microservices in e-commerce results in smaller, fine-grained services, such as display product service, update display service, and user default service in the product catalog application.', 'Common features like the display image server are shared across multiple applications in a microservices architecture, improving reusability and modularity. Common features like the display image server are shared across multiple applications in a microservices architecture, improving reusability and modularity.']}, {'end': 1119.1, 'start': 888.472, 'title': 'Microservices vs. soa shopping apps', 'summary': 'Highlights the differences between microservices and soa shopping applications, emphasizing the advantages of microservices in simplifying code changes and deployments, as well as the suitability of soa for simple applications.', 'duration': 230.628, 'highlights': ['Microservices allow for easier code changes and deployments, reducing the need to test and deploy each application separately. Reduced time and effort in testing and deploying multiple applications.', 'SOA is suitable for simple applications with limited functionalities, avoiding the complexity of implementing microservices for such cases. Simplified development and maintenance for straightforward applications.', 'The chapter concludes that neither microservices nor SOA is universally better, with each being preferred in different contexts. Acknowledgment of the contextual suitability of microservices and SOA.']}], 'duration': 400.3, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/EpyPFnjue38/pics/EpyPFnjue38718800.jpg', 'highlights': ['Microservices involve breaking down feature-level services into task-level services, such as separate billing and shipping options services in the shopping application.', 'The concept of microservices in e-commerce results in smaller, fine-grained services, such as display product service, update display service, and user default service in the product catalog application.', 'Common features like the display image server are shared across multiple applications in a microservices architecture, improving reusability and modularity.', 'Microservices allow for easier code changes and deployments, reducing the need to test and deploy each application separately.', 'SOA is suitable for simple applications with limited functionalities, avoiding the complexity of implementing microservices for such cases.', 'The chapter concludes that neither microservices nor SOA is universally better, with each being preferred in different contexts.']}], 'highlights': ['Monolithic applications are inflexible, unreliable, and slow to develop, hindering scalability and continuous development.', 'SOA and microservices offer flexibility, scalability, and the ability to use different technologies, enabling continuous development and better fit for complex architecture.', 'Microservices involve breaking down feature-level services into task-level services, such as separate billing and shipping options services in the shopping application.', 'SOA utilizes messaging middleware for diverse language interaction.', 'Microservices enable direct communication through REST APIs.', 'SOA is course-grained architecture where different services and features are broken down into smaller components, with multiple tasks delivered as one feature.', 'Microservices are fine-grained architecture where features or services are further broken down into task-level services, with multiple tasks and services in a microservice architecture.', 'SOA consists of four types of services: business, enterprise, application, and infrastructure, delivering software applications together.', 'Microservices have separate application-specific services and databases.', 'The concept of microservices in e-commerce results in smaller, fine-grained services, such as display product service, update display service, and user default service in the product catalog application.']}