SOA involves breaking large applications into smaller, independent services that communicate with each other, while monolith architecture keeps all application code and components together within a single codebase; services in SOA should have well-defined interfaces and be loosely coupled, stateless, and reusable; components of SOA include services, service consumers, registries, transports, and protocols like SOAP and REST that allow services to communicate.
This document provides an overview of service-oriented architecture (SOA) and microservice architecture. It defines SOA as an approach that makes software components reusable via well-defined service interfaces. SOA aims to make it easy for businesses to grow by adding new interoperable services. Microservice architecture is described as a variant of SOA where applications are composed of many small, independent services. The document also discusses SOA principles, components, integration strategies and key drivers for adopting SOA in enterprises.
Service Oriented Architecture.
SOA is a style of architecting applications in such a way that they are composed of discrete software agents that have simple, well defined interfaces and are orchestrated through a loose coupling to perform a required function.
The document provides information about Service Oriented Architecture (SOA). It discusses the characteristics, principles, evolution and comparison of SOA with past architectures like client-server and distributed architectures. Some key points include:
- SOA decomposes automation logic into smaller distinct units called services.
- It evolved from XML, then web services, and is now modeled with three components - service requestor, provider and registry.
- Services encapsulate logic and relate/communicate through service descriptions and messages.
- Common characteristics of SOA include being autonomous, using open standards, supporting vendor diversity, discovery, interoperability and loose coupling.
- SOA is compared to past application and enterprise architectures and
The document discusses the key components of Service Oriented Architecture (SOA). SOA is based on coarse-grained services that expose their capabilities through standardized interfaces and messages. The core SOA components are:
1) Services which implement discrete pieces of application logic and are autonomous, reusable modules accessible via messages.
2) Service contracts which define the messages and interfaces that a service supports.
3) Endpoints which are addresses where services can be accessed.
4) Messages which are the units of communication between services in the form of requests and responses.
5) Policies which govern a service's behavior and are set externally to the service.
6) Service consumers which interact with
SOA - Unit 2 - Service Oriented Architecturehamsa nandhini
This document discusses key concepts of service-oriented architecture (SOA), including common service delivery approaches, SOA concepts, and key SOA elements. It also covers SOA processes, principles, services, service contracts, and the technical and business benefits of implementing an SOA.
The document provides an introduction and overview of SOA (Service Oriented Architecture) concepts from the perspective of the author's experience working with SOA over many years. It discusses key SOA principles like reuse, flexibility and loose coupling. It also examines different approaches to service orientation and defines criteria for evaluating whether a system is truly service oriented. The importance of defining good service interfaces and contracts is emphasized.
Service oriented architecture characteristics of soasmithaps4
Service-oriented architecture (SOA) is a design pattern for building distributed systems using services. A service is a self-contained function that can be used by applications and other services. SOA uses loosely coupled, message-based communication between services. Contemporary SOA promotes qualities like autonomy, interoperability, reuse, and loose coupling through standardized service interfaces and compositions.
This document provides an overview of service-oriented architecture (SOA) and microservice architecture. It defines SOA as an approach that makes software components reusable via well-defined service interfaces. SOA aims to make it easy for businesses to grow by adding new interoperable services. Microservice architecture is described as a variant of SOA where applications are composed of many small, independent services. The document also discusses SOA principles, components, integration strategies and key drivers for adopting SOA in enterprises.
Service Oriented Architecture.
SOA is a style of architecting applications in such a way that they are composed of discrete software agents that have simple, well defined interfaces and are orchestrated through a loose coupling to perform a required function.
The document provides information about Service Oriented Architecture (SOA). It discusses the characteristics, principles, evolution and comparison of SOA with past architectures like client-server and distributed architectures. Some key points include:
- SOA decomposes automation logic into smaller distinct units called services.
- It evolved from XML, then web services, and is now modeled with three components - service requestor, provider and registry.
- Services encapsulate logic and relate/communicate through service descriptions and messages.
- Common characteristics of SOA include being autonomous, using open standards, supporting vendor diversity, discovery, interoperability and loose coupling.
- SOA is compared to past application and enterprise architectures and
The document discusses the key components of Service Oriented Architecture (SOA). SOA is based on coarse-grained services that expose their capabilities through standardized interfaces and messages. The core SOA components are:
1) Services which implement discrete pieces of application logic and are autonomous, reusable modules accessible via messages.
2) Service contracts which define the messages and interfaces that a service supports.
3) Endpoints which are addresses where services can be accessed.
4) Messages which are the units of communication between services in the form of requests and responses.
5) Policies which govern a service's behavior and are set externally to the service.
6) Service consumers which interact with
SOA - Unit 2 - Service Oriented Architecturehamsa nandhini
This document discusses key concepts of service-oriented architecture (SOA), including common service delivery approaches, SOA concepts, and key SOA elements. It also covers SOA processes, principles, services, service contracts, and the technical and business benefits of implementing an SOA.
The document provides an introduction and overview of SOA (Service Oriented Architecture) concepts from the perspective of the author's experience working with SOA over many years. It discusses key SOA principles like reuse, flexibility and loose coupling. It also examines different approaches to service orientation and defines criteria for evaluating whether a system is truly service oriented. The importance of defining good service interfaces and contracts is emphasized.
Service oriented architecture characteristics of soasmithaps4
Service-oriented architecture (SOA) is a design pattern for building distributed systems using services. A service is a self-contained function that can be used by applications and other services. SOA uses loosely coupled, message-based communication between services. Contemporary SOA promotes qualities like autonomy, interoperability, reuse, and loose coupling through standardized service interfaces and compositions.
SOA1-Background.ppt SOFTWARE ORIENTED SERVICES AND ARCHITECTUREAnyaForger34
This document provides an overview of service orientation and service-oriented architecture (SOA) in three sessions. The first session introduces service orientation, contrasts it with other architectural styles like resource-oriented and object-oriented architectures, and provides examples of service-oriented architectures. It also discusses web services, their motivation and evolution. Key points covered are that service orientation models business needs better through loose coupling and dynamic binding. SOA allows flexibility, reuse, and cost efficiency. Legacy systems can be integrated using SOA. The document discusses characteristics of services, elements of SOA, and benefits of adopting SOA. Examples of SOA frameworks discussed are Jini and web services.
This document discusses service-oriented architecture (SOA). It defines SOA as a style of software design where discrete units of functionality (services) can be accessed remotely over a network to form applications. Services must be self-contained, independent of vendors/products, and able to represent business activities. SOA allows components to communicate and cooperate over a network using standards and technologies. It also discusses the roles of service providers, brokers/registries, and requesters/consumers. Benefits of SOA include reusability, simplifying legacy system integration, and giving organizations more control over problem-solving in a standardized way.
Introduction to Service Oriented Architectures, SOAP/WSDL Web Services and RE...ecosio GmbH
In this guest talk, held as part of the Web Engineering lecture series at Vienna University of Technology, we give an overview of the current state of the art in the domain of Web Services.
In the first part we dwell on the main principles of Service Oriented Architectures (SOA), followed by an introduction of the three core standards SOAP, WSDL, as well as UDDI. Furthermore, we briefly cover the Java API for XML Web Services (JAX-WS).
In the second part we focus on principles of RESTful Web Services and the Java API for RESTful Web Services. The lecture is accompanied by practical examples, which are also available on GitHub.
Cloud networks utilize remote servers and the internet rather than local servers or personal computers to store, manage and process data. They offer scalability, flexibility and cost savings through virtualization, resource pooling and pay-per-use billing models. Managed service providers help organizations manage their IT infrastructure through services like monitoring, support, security and compliance management. They work to fill staffing gaps and improve organizations' security, cost efficiency and business continuity. Open source software plays a key role in cloud computing through components used for web presence, databases, application servers and more.
A Service-Oriented Architecture (SOA) is a system consisting of software components with standardized component-access and usage interfaces that are independent of any specific platform or implementation technology and it's solution for making two software to communicate to each other.
Service-oriented Architecture with Respect to ReusabilityYazd University
This document provides an introduction to service-oriented development with a focus on reusability. It includes 4 lectures on topics like introduction to service-oriented architecture, reusability and its relation to SOA, SOA tools, and SOA case studies. The lectures are presented by group members from Shahid Bahonar University of Kerman and cover concepts such as SOA, web services, the SOA lifecycle, and SOA design patterns.
Service-oriented architecture (SOA) emphasizes using services as components that can be accessed and utilized independently. In a cloud-based SOA architecture, modular services are designed to be interoperable and reusable across applications. These services are accessed through web APIs and can be easily deployed, updated, and scaled on demand in the cloud to meet changing needs. Combining SOA with cloud computing provides organizations with a flexible, scalable approach to building software systems.
The document discusses service-oriented computing and programming models in cloud computing. It begins by explaining the limitations of monolithic application architectures and how service-oriented computing addresses them by decomposing applications into loosely coupled, independent services. It then defines services and service-oriented architecture (SOA), including their key characteristics and components. The document also covers web services, different types of web service protocols like SOAP and RESTful, and how SOA relates to cloud computing. It discusses microservices architecture and programming models like MapReduce. Finally, it explains coordination models and different Hadoop scheduling algorithms.
This document discusses service-oriented architecture (SOA) in banking and outlines some key benefits and challenges. SOA can benefit banking by enabling customer information management across systems, multi-channel integration, operational excellence through business process automation, and intelligent inbound cross-selling. However, performance issues may arise with SOA implementations due to their distributed nature. To address this, the document emphasizes the importance of service level agreements, infrastructure capacity planning, SOA performance testing, and monitoring systems to ensure performance meets requirements.
This document discusses service-oriented architecture (SOA). It defines SOA as an architecture based on reusable services that are loosely coupled and provide platform, technology, and language independence. The document outlines SOA principles like standardized service contracts, loose coupling, abstraction, and others. It also discusses SOA implementation steps, the value of SOA for businesses and technologies, and when SOA may not be recommended.
The document discusses Service Oriented Architecture (SOA) and the Business Process Execution Language (BPEL). It defines SOA as an architectural style that allows for interoperability and flexibility. BPEL is introduced as an XML-based language used to specify business processes composed of discrete web services. Key concepts covered include the need for SOA to address heterogeneous systems and changing business needs, the role of services, and how BPEL allows the orchestration of services to create composite applications and implement business processes.
The document discusses Service Oriented Architecture (SOA) and the role of the Business Process Execution Language (BPEL). It defines SOA as an architectural style that allows components to work together through standardized interfaces. BPEL is presented as an XML-based language used to specify business processes composed of discrete web services. BPEL allows the orchestration of services by defining message sequences and processing logic. It bridges the bottom-up exposure of services and the top-down definition of business processes in SOA.
Cloud computing allows users to access computing resources over the network. It has several key characteristics including on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service. There are three main service models (Software as a Service, Platform as a Service, and Infrastructure as a Service) and four deployment models (private cloud, community cloud, public cloud, and hybrid cloud). Achieving high performance, availability, and manageability in cloud computing requires techniques like virtualization, parallel processing, fault tolerance, load balancing and automation.
إن الحوسبة السحابية تعني توفير موارد تقنية المعلومات حسب الطلب عبر الإنترنت مع تسعير التكلفة حسب الاستخدام. فبدلاً من شراء مراكز البيانات الفعلية وامتلاكها والاحتفاظ بها، يمكنك الاستفادة من الخدمات التكنولوجية، مثل إمكانيات الحوسبة، والتخزين، وقواعد البيانات، بأسلوب يعتمد على الاحتياجات لديك، وذلك من خلال جهة موفرة للخدمات السحابية مثل Amazon Web Services (AWS
The document discusses Service Oriented Architecture (SOA). It defines SOA as a collection of services that communicate with each other. These communication units are called services. Communication can involve simple data passing or coordinating an activity between two or more services. The document also discusses the evolution of SOA including the roles of XML, web services, and how SOA is defined with service requestors, providers, and registries. Key characteristics of SOA are also outlined such as being service-based, specification-based, combinable, reusable, and more. Past architectures like client-server and distributed architectures are also compared to SOA.
Web services use open standards like XML, SOAP, WSDL and UDDI to allow applications to communicate over the web. SOAP defines how to structure XML messages for web services to exchange information. RESTful web services use HTTP requests to access web resources and support different data formats like XML and JSON. Reliable messaging ensures messages are received exactly once and in order through acknowledgements.
'A View-Based Approach to Quality of Service Modelling in Service-Oriented En...IIBA_Latvia_Chapter
This document proposes a view-based framework to model quality of service (QoS) in service-oriented enterprise systems. It notes that current QoS modeling is too technology-focused and ignores other perspectives like business needs. The research aims to balance viewpoints by constructing multiple views of QoS, modeling each as interacting goals, and using techniques like i* modeling to balance conflicts across views. This holistic approach would provide a more comprehensive QoS model for controlled enterprise systems compared to open internet-based service-oriented architectures.
Rod Johnson created the Spring Framework, an open-source Java application framework. Spring is considered a flexible, low-cost framework that improves coding efficiency. It helps developers perform functions like creating database transaction methods without transaction APIs. Spring removes configuration work so developers can focus on writing business logic. The Spring Framework uses inversion of control (IoC) and dependency injection (DI) principles to manage application objects and dependencies between them.
The document discusses REST (REpresentational State Transfer) APIs. It defines REST as a style of architecture for distributed hypermedia systems, including definitions of resources, URIs to identify resources, and HTTP methods like GET, POST, PUT, DELETE to operate on resources. It describes key REST concepts like resources, URIs, requests and responses, and architectural constraints like being stateless and cacheable. It provides examples of defining resources and URIs for a blog application API.
Weitere ähnliche Inhalte
Ähnlich wie SOA and Monolith Architecture - Micro Services.pptx
SOA1-Background.ppt SOFTWARE ORIENTED SERVICES AND ARCHITECTUREAnyaForger34
This document provides an overview of service orientation and service-oriented architecture (SOA) in three sessions. The first session introduces service orientation, contrasts it with other architectural styles like resource-oriented and object-oriented architectures, and provides examples of service-oriented architectures. It also discusses web services, their motivation and evolution. Key points covered are that service orientation models business needs better through loose coupling and dynamic binding. SOA allows flexibility, reuse, and cost efficiency. Legacy systems can be integrated using SOA. The document discusses characteristics of services, elements of SOA, and benefits of adopting SOA. Examples of SOA frameworks discussed are Jini and web services.
This document discusses service-oriented architecture (SOA). It defines SOA as a style of software design where discrete units of functionality (services) can be accessed remotely over a network to form applications. Services must be self-contained, independent of vendors/products, and able to represent business activities. SOA allows components to communicate and cooperate over a network using standards and technologies. It also discusses the roles of service providers, brokers/registries, and requesters/consumers. Benefits of SOA include reusability, simplifying legacy system integration, and giving organizations more control over problem-solving in a standardized way.
Introduction to Service Oriented Architectures, SOAP/WSDL Web Services and RE...ecosio GmbH
In this guest talk, held as part of the Web Engineering lecture series at Vienna University of Technology, we give an overview of the current state of the art in the domain of Web Services.
In the first part we dwell on the main principles of Service Oriented Architectures (SOA), followed by an introduction of the three core standards SOAP, WSDL, as well as UDDI. Furthermore, we briefly cover the Java API for XML Web Services (JAX-WS).
In the second part we focus on principles of RESTful Web Services and the Java API for RESTful Web Services. The lecture is accompanied by practical examples, which are also available on GitHub.
Cloud networks utilize remote servers and the internet rather than local servers or personal computers to store, manage and process data. They offer scalability, flexibility and cost savings through virtualization, resource pooling and pay-per-use billing models. Managed service providers help organizations manage their IT infrastructure through services like monitoring, support, security and compliance management. They work to fill staffing gaps and improve organizations' security, cost efficiency and business continuity. Open source software plays a key role in cloud computing through components used for web presence, databases, application servers and more.
A Service-Oriented Architecture (SOA) is a system consisting of software components with standardized component-access and usage interfaces that are independent of any specific platform or implementation technology and it's solution for making two software to communicate to each other.
Service-oriented Architecture with Respect to ReusabilityYazd University
This document provides an introduction to service-oriented development with a focus on reusability. It includes 4 lectures on topics like introduction to service-oriented architecture, reusability and its relation to SOA, SOA tools, and SOA case studies. The lectures are presented by group members from Shahid Bahonar University of Kerman and cover concepts such as SOA, web services, the SOA lifecycle, and SOA design patterns.
Service-oriented architecture (SOA) emphasizes using services as components that can be accessed and utilized independently. In a cloud-based SOA architecture, modular services are designed to be interoperable and reusable across applications. These services are accessed through web APIs and can be easily deployed, updated, and scaled on demand in the cloud to meet changing needs. Combining SOA with cloud computing provides organizations with a flexible, scalable approach to building software systems.
The document discusses service-oriented computing and programming models in cloud computing. It begins by explaining the limitations of monolithic application architectures and how service-oriented computing addresses them by decomposing applications into loosely coupled, independent services. It then defines services and service-oriented architecture (SOA), including their key characteristics and components. The document also covers web services, different types of web service protocols like SOAP and RESTful, and how SOA relates to cloud computing. It discusses microservices architecture and programming models like MapReduce. Finally, it explains coordination models and different Hadoop scheduling algorithms.
This document discusses service-oriented architecture (SOA) in banking and outlines some key benefits and challenges. SOA can benefit banking by enabling customer information management across systems, multi-channel integration, operational excellence through business process automation, and intelligent inbound cross-selling. However, performance issues may arise with SOA implementations due to their distributed nature. To address this, the document emphasizes the importance of service level agreements, infrastructure capacity planning, SOA performance testing, and monitoring systems to ensure performance meets requirements.
This document discusses service-oriented architecture (SOA). It defines SOA as an architecture based on reusable services that are loosely coupled and provide platform, technology, and language independence. The document outlines SOA principles like standardized service contracts, loose coupling, abstraction, and others. It also discusses SOA implementation steps, the value of SOA for businesses and technologies, and when SOA may not be recommended.
The document discusses Service Oriented Architecture (SOA) and the Business Process Execution Language (BPEL). It defines SOA as an architectural style that allows for interoperability and flexibility. BPEL is introduced as an XML-based language used to specify business processes composed of discrete web services. Key concepts covered include the need for SOA to address heterogeneous systems and changing business needs, the role of services, and how BPEL allows the orchestration of services to create composite applications and implement business processes.
The document discusses Service Oriented Architecture (SOA) and the role of the Business Process Execution Language (BPEL). It defines SOA as an architectural style that allows components to work together through standardized interfaces. BPEL is presented as an XML-based language used to specify business processes composed of discrete web services. BPEL allows the orchestration of services by defining message sequences and processing logic. It bridges the bottom-up exposure of services and the top-down definition of business processes in SOA.
Cloud computing allows users to access computing resources over the network. It has several key characteristics including on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service. There are three main service models (Software as a Service, Platform as a Service, and Infrastructure as a Service) and four deployment models (private cloud, community cloud, public cloud, and hybrid cloud). Achieving high performance, availability, and manageability in cloud computing requires techniques like virtualization, parallel processing, fault tolerance, load balancing and automation.
إن الحوسبة السحابية تعني توفير موارد تقنية المعلومات حسب الطلب عبر الإنترنت مع تسعير التكلفة حسب الاستخدام. فبدلاً من شراء مراكز البيانات الفعلية وامتلاكها والاحتفاظ بها، يمكنك الاستفادة من الخدمات التكنولوجية، مثل إمكانيات الحوسبة، والتخزين، وقواعد البيانات، بأسلوب يعتمد على الاحتياجات لديك، وذلك من خلال جهة موفرة للخدمات السحابية مثل Amazon Web Services (AWS
The document discusses Service Oriented Architecture (SOA). It defines SOA as a collection of services that communicate with each other. These communication units are called services. Communication can involve simple data passing or coordinating an activity between two or more services. The document also discusses the evolution of SOA including the roles of XML, web services, and how SOA is defined with service requestors, providers, and registries. Key characteristics of SOA are also outlined such as being service-based, specification-based, combinable, reusable, and more. Past architectures like client-server and distributed architectures are also compared to SOA.
Web services use open standards like XML, SOAP, WSDL and UDDI to allow applications to communicate over the web. SOAP defines how to structure XML messages for web services to exchange information. RESTful web services use HTTP requests to access web resources and support different data formats like XML and JSON. Reliable messaging ensures messages are received exactly once and in order through acknowledgements.
'A View-Based Approach to Quality of Service Modelling in Service-Oriented En...IIBA_Latvia_Chapter
This document proposes a view-based framework to model quality of service (QoS) in service-oriented enterprise systems. It notes that current QoS modeling is too technology-focused and ignores other perspectives like business needs. The research aims to balance viewpoints by constructing multiple views of QoS, modeling each as interacting goals, and using techniques like i* modeling to balance conflicts across views. This holistic approach would provide a more comprehensive QoS model for controlled enterprise systems compared to open internet-based service-oriented architectures.
Ähnlich wie SOA and Monolith Architecture - Micro Services.pptx (20)
Rod Johnson created the Spring Framework, an open-source Java application framework. Spring is considered a flexible, low-cost framework that improves coding efficiency. It helps developers perform functions like creating database transaction methods without transaction APIs. Spring removes configuration work so developers can focus on writing business logic. The Spring Framework uses inversion of control (IoC) and dependency injection (DI) principles to manage application objects and dependencies between them.
The document discusses REST (REpresentational State Transfer) APIs. It defines REST as a style of architecture for distributed hypermedia systems, including definitions of resources, URIs to identify resources, and HTTP methods like GET, POST, PUT, DELETE to operate on resources. It describes key REST concepts like resources, URIs, requests and responses, and architectural constraints like being stateless and cacheable. It provides examples of defining resources and URIs for a blog application API.
The application layer sits at Layer 7, the top of the Open Systems Interconnection (OSI) communications model. It ensures an application can effectively communicate with other applications on different computer systems and networks. The application layer is not an application.
The document discusses connecting Node.js applications to NoSQL MongoDB databases using Mongoose. It begins with an introduction to MongoDB and NoSQL databases. It then covers how to install Mongoose and connect a Node.js application to a MongoDB database. It provides examples of performing CRUD operations in MongoDB using Mongoose, including inserting, updating, and deleting documents.
Node.js supports JavaScript syntax and uses modules to organize code. There are three types of modules - core modules which are built-in, local modules within the project, and third-party modules. Core modules like HTTP and file system (FS) provide key functionalities. To create a basic HTTP server, the HTTP core module is required, a server is set up to listen on a port using createServer(), and requests are handled using the request and response objects.
The navigation bar connects all relevant website pages through links, allowing users to easily navigate between them. It displays page names and links in an accessible searchable format. Bootstrap provides the '.navbar' class to create navigation bars that are fluid and responsive by default. Forms collect and update user information through interactive elements like text fields, checkboxes, and buttons. Bootstrap supports stacked and inline forms, and input groups enhance form fields with prepended or appended text using the '.input-group' and '.input-group-text' classes.
The document describes 3 steps to use Bootstrap offline:
1. Download the compiled CSS and JS files from Bootstrap and extract them locally. Reference the local files in an HTML document instead of CDN links.
2. Bootstrap depends on jQuery, so download the compressed jQuery file and save it in the Bootstrap JS folder for the Bootstrap code to work offline.
3. As an alternative to manually downloading the files, the Bootstrap directory can be downloaded using NPM which will package all necessary dependencies.
This document discusses several Java programming concepts including nested classes, object parameters, recursion, and command line arguments. Nested classes allow a class to be declared within another class and access private members of the outer class. Objects can be passed as parameters to methods, allowing the method to modify the object's fields. Recursion is when a method calls itself, such as a recursive method to calculate factorials. Command line arguments allow passing input to a program when running it from the command line.
This document provides an overview of social network analysis. It defines key concepts like nodes, edges, degrees, and centrality measures. It describes different types of networks including full networks, egocentric networks, affiliation networks, and multiplex networks. It also outlines common network analysis metrics that can be used to analyze networks at both the aggregate and individual level. These include measures like density, degree centrality, betweenness centrality, closeness centrality, and eigenvector centrality. The document discusses tools for social network analysis and ways of visually mapping social networks.
This document provides an overview of social media and social networks. It discusses key dimensions of social media systems including size of producer/consumer populations, pace of interaction, genre of basic elements, control of elements, types of connections, and retention of content. Examples are given for different social media types like asynchronous/synchronous conversations, social sharing, social networking, online markets, web/collaborative authoring, and blogs/podcasts. The rise of social media and how it has changed communication is also examined.
The document discusses different types of menus that can be created using CSS and HTML, including vertical menus, horizontal menus, and drop-down menus. Vertical menus are created by adding links to an unordered list, while horizontal menus require setting the list items to display inline. Drop-down menus use the HTML select and option tags within a form to allow users to select an option from a dropdown list.
The <div> tag defines sections on an HTML page and is used to group other elements. It has no inherent styling but can be styled using classes, IDs, or inline styles. Any content can be placed inside a <div> tag, which browsers separate with line breaks. Examples are provided of using <div> tags with inline and external styles to format text sections with different backgrounds and fonts.
This document discusses CSS properties for controlling the dimensions and borders of elements. It describes properties for setting border style (solid, dotted, etc.), width, height, padding, margins, and more. Code examples are provided to demonstrate how to use these properties to specify the dimensions and spacing around elements. The CSS box model is also explained, which considers HTML elements as boxes made up of content, padding, border, and margin.
This document discusses different CSS positioning methods including fixed, absolute, relative, static, and sticky positioning. It provides code examples to demonstrate how each positioning method works. Fixed positioning positions an element relative to the browser window, absolute positioning positions elements relative to the screen, relative positioning positions elements relative to their normal position, and static positioning is the default that positions elements in normal flow without affecting positioning properties. Sticky positioning positions elements based on the user's scroll position.
This document discusses how to generate random numbers in JavaScript using the Math.random() function. It explains that Math.random() returns a random number between 0 (inclusive) and 1 (exclusive) and how to scale the random number to a desired range. It provides examples of generating random numbers between 0 and a max value, within a range of values, and as integers between a min and max value. The document also demonstrates how to display random images by selecting a random index from an array of image sources.
The document provides an introduction to JavaScript including:
- JavaScript is a lightweight, object-oriented programming language used to add interactivity to webpages. It was introduced in 1995 to enable dynamic content in web browsers.
- Popular features of JavaScript include support across web browsers, a C-like syntax, weak typing, prototype-based inheritance, and client-side scripting abilities.
- Common applications of JavaScript include client-side form validation, dynamic menus, displaying clocks/dates, and pop-up boxes. It allows users to build interactive web applications without page reloads.
Quality of service (QoS) refers to a network's ability to achieve maximum bandwidth and handle factors like latency, error rate, and uptime. QoS involves controlling network resources by prioritizing specific data types and four key characteristics are reliability, delay, jitter, and bandwidth. Flow control techniques like scheduling, traffic shaping, resource reservation, and admission control help improve QoS.
The document discusses the key functions and protocols of the transport layer. It describes how the transport layer establishes end-to-end connections between hosts, delivers data through encapsulation and multiplexing, and provides services like flow control, error control, and congestion control. The major transport layer protocols are TCP and UDP, with TCP providing connection-oriented and reliable data transfer, and UDP being connectionless.
1. The document discusses the Transport Layer protocols TCP and UDP. TCP provides connection-oriented and reliable transmission, while UDP provides connectionless and unreliable transmission.
2. TCP establishes connections between processes using three-way handshaking and provides flow control, error checking, and retransmission of lost packets to ensure reliable delivery.
3. UDP is a simpler protocol that does not establish connections or ensure delivery. It is used for applications that require low-latency transmission and can tolerate some data loss.
Mehr von Kongu Engineering College, Perundurai, Erode (20)
Redefining brain tumor segmentation: a cutting-edge convolutional neural netw...IJECEIAES
Medical image analysis has witnessed significant advancements with deep learning techniques. In the domain of brain tumor segmentation, the ability to
precisely delineate tumor boundaries from magnetic resonance imaging (MRI)
scans holds profound implications for diagnosis. This study presents an ensemble convolutional neural network (CNN) with transfer learning, integrating
the state-of-the-art Deeplabv3+ architecture with the ResNet18 backbone. The
model is rigorously trained and evaluated, exhibiting remarkable performance
metrics, including an impressive global accuracy of 99.286%, a high-class accuracy of 82.191%, a mean intersection over union (IoU) of 79.900%, a weighted
IoU of 98.620%, and a Boundary F1 (BF) score of 83.303%. Notably, a detailed comparative analysis with existing methods showcases the superiority of
our proposed model. These findings underscore the model’s competence in precise brain tumor localization, underscoring its potential to revolutionize medical
image analysis and enhance healthcare outcomes. This research paves the way
for future exploration and optimization of advanced CNN models in medical
imaging, emphasizing addressing false positives and resource efficiency.
Design and optimization of ion propulsion dronebjmsejournal
Electric propulsion technology is widely used in many kinds of vehicles in recent years, and aircrafts are no exception. Technically, UAVs are electrically propelled but tend to produce a significant amount of noise and vibrations. Ion propulsion technology for drones is a potential solution to this problem. Ion propulsion technology is proven to be feasible in the earth’s atmosphere. The study presented in this article shows the design of EHD thrusters and power supply for ion propulsion drones along with performance optimization of high-voltage power supply for endurance in earth’s atmosphere.
Batteries -Introduction – Types of Batteries – discharging and charging of battery - characteristics of battery –battery rating- various tests on battery- – Primary battery: silver button cell- Secondary battery :Ni-Cd battery-modern battery: lithium ion battery-maintenance of batteries-choices of batteries for electric vehicle applications.
Fuel Cells: Introduction- importance and classification of fuel cells - description, principle, components, applications of fuel cells: H2-O2 fuel cell, alkaline fuel cell, molten carbonate fuel cell and direct methanol fuel cells.
Use PyCharm for remote debugging of WSL on a Windo cf5c162d672e4e58b4dde5d797...shadow0702a
This document serves as a comprehensive step-by-step guide on how to effectively use PyCharm for remote debugging of the Windows Subsystem for Linux (WSL) on a local Windows machine. It meticulously outlines several critical steps in the process, starting with the crucial task of enabling permissions, followed by the installation and configuration of WSL.
The guide then proceeds to explain how to set up the SSH service within the WSL environment, an integral part of the process. Alongside this, it also provides detailed instructions on how to modify the inbound rules of the Windows firewall to facilitate the process, ensuring that there are no connectivity issues that could potentially hinder the debugging process.
The document further emphasizes on the importance of checking the connection between the Windows and WSL environments, providing instructions on how to ensure that the connection is optimal and ready for remote debugging.
It also offers an in-depth guide on how to configure the WSL interpreter and files within the PyCharm environment. This is essential for ensuring that the debugging process is set up correctly and that the program can be run effectively within the WSL terminal.
Additionally, the document provides guidance on how to set up breakpoints for debugging, a fundamental aspect of the debugging process which allows the developer to stop the execution of their code at certain points and inspect their program at those stages.
Finally, the document concludes by providing a link to a reference blog. This blog offers additional information and guidance on configuring the remote Python interpreter in PyCharm, providing the reader with a well-rounded understanding of the process.
Rainfall intensity duration frequency curve statistical analysis and modeling...bijceesjournal
Using data from 41 years in Patna’ India’ the study’s goal is to analyze the trends of how often it rains on a weekly, seasonal, and annual basis (1981−2020). First, utilizing the intensity-duration-frequency (IDF) curve and the relationship by statistically analyzing rainfall’ the historical rainfall data set for Patna’ India’ during a 41 year period (1981−2020), was evaluated for its quality. Changes in the hydrologic cycle as a result of increased greenhouse gas emissions are expected to induce variations in the intensity, length, and frequency of precipitation events. One strategy to lessen vulnerability is to quantify probable changes and adapt to them. Techniques such as log-normal, normal, and Gumbel are used (EV-I). Distributions were created with durations of 1, 2, 3, 6, and 24 h and return times of 2, 5, 10, 25, and 100 years. There were also mathematical correlations discovered between rainfall and recurrence interval.
Findings: Based on findings, the Gumbel approach produced the highest intensity values, whereas the other approaches produced values that were close to each other. The data indicates that 461.9 mm of rain fell during the monsoon season’s 301st week. However, it was found that the 29th week had the greatest average rainfall, 92.6 mm. With 952.6 mm on average, the monsoon season saw the highest rainfall. Calculations revealed that the yearly rainfall averaged 1171.1 mm. Using Weibull’s method, the study was subsequently expanded to examine rainfall distribution at different recurrence intervals of 2, 5, 10, and 25 years. Rainfall and recurrence interval mathematical correlations were also developed. Further regression analysis revealed that short wave irrigation, wind direction, wind speed, pressure, relative humidity, and temperature all had a substantial influence on rainfall.
Originality and value: The results of the rainfall IDF curves can provide useful information to policymakers in making appropriate decisions in managing and minimizing floods in the study area.
Applications of artificial Intelligence in Mechanical Engineering.pdfAtif Razi
Historically, mechanical engineering has relied heavily on human expertise and empirical methods to solve complex problems. With the introduction of computer-aided design (CAD) and finite element analysis (FEA), the field took its first steps towards digitization. These tools allowed engineers to simulate and analyze mechanical systems with greater accuracy and efficiency. However, the sheer volume of data generated by modern engineering systems and the increasing complexity of these systems have necessitated more advanced analytical tools, paving the way for AI.
AI offers the capability to process vast amounts of data, identify patterns, and make predictions with a level of speed and accuracy unattainable by traditional methods. This has profound implications for mechanical engineering, enabling more efficient design processes, predictive maintenance strategies, and optimized manufacturing operations. AI-driven tools can learn from historical data, adapt to new information, and continuously improve their performance, making them invaluable in tackling the multifaceted challenges of modern mechanical engineering.
Embedded machine learning-based road conditions and driving behavior monitoringIJECEIAES
Car accident rates have increased in recent years, resulting in losses in human lives, properties, and other financial costs. An embedded machine learning-based system is developed to address this critical issue. The system can monitor road conditions, detect driving patterns, and identify aggressive driving behaviors. The system is based on neural networks trained on a comprehensive dataset of driving events, driving styles, and road conditions. The system effectively detects potential risks and helps mitigate the frequency and impact of accidents. The primary goal is to ensure the safety of drivers and vehicles. Collecting data involved gathering information on three key road events: normal street and normal drive, speed bumps, circular yellow speed bumps, and three aggressive driving actions: sudden start, sudden stop, and sudden entry. The gathered data is processed and analyzed using a machine learning system designed for limited power and memory devices. The developed system resulted in 91.9% accuracy, 93.6% precision, and 92% recall. The achieved inference time on an Arduino Nano 33 BLE Sense with a 32-bit CPU running at 64 MHz is 34 ms and requires 2.6 kB peak RAM and 139.9 kB program flash memory, making it suitable for resource-constrained embedded systems.
An improved modulation technique suitable for a three level flying capacitor ...IJECEIAES
This research paper introduces an innovative modulation technique for controlling a 3-level flying capacitor multilevel inverter (FCMLI), aiming to streamline the modulation process in contrast to conventional methods. The proposed
simplified modulation technique paves the way for more straightforward and
efficient control of multilevel inverters, enabling their widespread adoption and
integration into modern power electronic systems. Through the amalgamation of
sinusoidal pulse width modulation (SPWM) with a high-frequency square wave
pulse, this controlling technique attains energy equilibrium across the coupling
capacitor. The modulation scheme incorporates a simplified switching pattern
and a decreased count of voltage references, thereby simplifying the control
algorithm.
An improved modulation technique suitable for a three level flying capacitor ...
SOA and Monolith Architecture - Micro Services.pptx
1. SOA and Monolith Architecture -
Micro Services
Types of software architectures
2. Software Architecture
•Designs the overall structure of the software
system
•It provides a strategic and structured approach
to building software systems
3. Software engineer & Software architect's
•Software Engineer is primarily responsible for the actual
coding or programming of the software.
•Using the software architect's design, the software engineer
translates the architectural plans into lines of code.
•A software engineer is the one who executes a plan that is
created by a software architect.
•Software Engineer utilizes an array of tools and
technologies, including programming languages like Python
or Java, development environments, version control
systems, and testing tools.
4. Software architect's
• Architects often have a broader view of the entire
system and are involved in making decisions about
technology stack, frameworks, and overall system
design
5. Real time example ( BookMyShow APP) – For Service
• BookMyShow is a popular platform for booking tickets for movies,
events, and plays.
• They often have promotional offers and deals that can help you save
money on your ticket purchases.
• Bookmyshow allows you to save your Debit/Credit card, Net
Banking, Gift Voucher, UPI or Redeem Points details under the
"Quick Pay" option. I
6. Example - Patient Management Systems
• healthcare organization, such as patient management systems and
electronic health record (EHR) systems, need to register patients.
These systems can call a single, common service to perform the
patient registration task.
7. What is Service?
• A service is a well-defined, self-contained function that
represents a unit of functionality.
• A service can exchange information from another service.
• It is not dependent on the state of another service.
• It uses a loosely coupled, message-based communication
model to communicate with applications and other services.
Service consumer sends a service request to the
service provider, and the service provider sends
the service response to the service consumer.
The service connection is understandable to both
the service consumer and service provider.
8. Service
• refers to a software functionality, or a set of software functionalities (such as
the retrieval of specified information or the execution of a set of operations)
with a purpose that different clients can reuse for different purposes,
together with the policies that should control its usage (based on the identity
of the client requesting the service
• One example is the separation of the business function "Manage Orders" into
services such as "Create Order", "Fulfill Order", "Ship Order", "Invoice
Order" and "Cancel/Update Order".
• These business functions have to have a granularity that is adequate in the
given project and domain context.
9. Service Oriented Architecture (SOA)
• In SOA, the large application is split up into multiple smaller services
that are deployed independently.
• is a method of software development that uses software components
called services to create business applications.
• Each service provides a business capability, and services can also
communicate with each other across platforms and languages.
• Developers use SOA to reuse services in different systems or combine
several independent services to perform complex tasks.
• It is an architectural design which includes collection of services in a
network which communicate with each other.
• It is a design pattern which is designed to build distributed systems that
deliver services to other applications through the protocol
• It is only a concept and not limited to any programming language or
platform.
10. Service Connections
• Services - one or more published interfaces.
• Service provider - implements a service
specification.
• Service consumer - called as a requestor or
client
• Service locator - It is a service provider that
acts as a registry. It is responsible for
examining service provider interfaces and
service locations.
• Service broker - that pass service requests to
one or more additional service providers.
11. Why to use SOA?
• SOA is widely used in market which responds quickly and makes effective
changes according to market situations.
• The SOA keep secret the implementation details of the subsystems.
• It allows interaction of new channels with customers, partners and
suppliers.
• It authorizes the companies to select software or hardware of their choice as
it acts as platform independence.
12. What are the basic principles of service-oriented
architecture?
• Interoperability-Each service in SOA includes description documents that
specify the functionality of the service and the related terms and
conditions
• Loose coupling -Services in SOA should be loosely coupled, having as little
dependency as possible on external resources such as data models or
information systems. They should also be stateless without retaining any
information from past sessions or transactions..
• Abstraction -Clients or service users in SOA need not know the service's
code logic or implementation details.
• Granularity -Services in SOA should have an appropriate size and scope,
ideally packing one discrete business function per service. Developers can
then use multiple services to create a composite service for performing
complex operations.
13. How does service-oriented architecture
work?
• In service-oriented architecture (SOA), services function independently
and provide functionality or data exchanges to their consumers.
• The consumer requests information and sends input data to the service.
• The service processes the data, performs the task, and sends back a
response.
• For example, if an application uses an authorization service, it gives the
service the username and password. The service verifies the username
and password and returns an appropriate response.
14. How does service-oriented architecture
work?
• The basic principles of service-oriented architecture are
independent of vendors, products and technologies.
• A service is a discrete unit of functionality that can be accessed
remotely and acted upon and updated independently, such as
retrieving a credit card statement online.
15. Communication protocols
• Services communicate using established rules that determine data
transmission over a network.
• These rules are called communication protocols.
• Some standard protocols to implement SOA include the following:
• Simple Object Access Protocol (SOAP) - is a way to pass information
between applications in an XML format.
• RESTful HTTP
• Apache Thrift
• Apache ActiveMQ
• Java Message Service (JMS)
16. Characteristics of SOA
• They are loosely coupled.
• They support interoperability.
• They are location-transparent
• They are self-contained.
17. Components of service-oriented architecture
Transport - the service requests from the service consumer to the
service provider and service responses from the service provider to the
service consumer.
Service Communication Protocol - It allows the service provider
and the service consumer to communicate with each other.
Service Description - It describes the service and data required to
invoke it.
Service - It is an actual service.
Business Process - It represents the group of services called in a
particular sequence associated with the particular rules to meet the
business requirements.
Service Registry - It contains the description of data which is used
by service providers to publish their services.
18. Components of service-oriented architecture
Quality of Service aspects
• Policy - It represents the set of protocols according to which a
service provider make and provide the services to consumers.
• Security - It represents the set of protocols required for
identification and authorization.
• Transaction - It provides the surety of consistent result. This
means, if we use the group of services to complete a business
function, either all must complete or none of the complete.
• Management - It defines the set of attributes used to manage
the services.
19. Business Activity
Monitoring(BAM)
used by the products
to display the runtime
details in the graphical
system.
The BAM products
includes adapters or
sensors which are used
to access the data
using the Java, PL/SQL
and other languages.
CEP stands for Complex Event
Processing which allows to
browse event streams based
on the certain pattern which
can be uncorrelated in time or
content.
ESB stands for Enterprise Service Bus which gives patterns that are
liable for the tasks and ranges from routing to reachability, allow the
interaction between message and protocol transformation and
manages the SOA environment.
20. Enterprise Service Bus (ESB)
• An Enterprise Service Bus (ESB) is a software product that provides a
platform for integrating various applications in a service-oriented
architecture (SOA) environment, managing web services, and
message brokering between them.
• ESB support the use of multiple protocols and message formats,
allowing different applications to communicate with each other
seamlessly.
• The best enterprise service bus depends on the specific needs of an
organization. Some popular ESB tools include MuleSoft, Apache
ServiceMix, and IBM Integration Bus.
21. Enterprise Service Bus (ESB)
• In a service-oriented architecture, APIs are exposed as web services made
available via specific formats and transports such as JMS or XML.
• An ESB is layered on top of those APIs to provide a more comprehensive
solution that includes message routing, transformation, mediation, security,
and so on.
• ESBs are designed for environments that involve multiple systems
communicating with each other, providing connections between services and
the clients that access them.
• ESBs are specifically designed for application integration in a service-
oriented environment.
22.
23. Banking Examples of SOA
Internet Banking
Business Process: Stop Payment
Registry and Repository: Find Stop Payment Service, Charge Fee service
Security: Authenticate user
Manage and monitor
ESB: Routes to appropriate core system
Data Services
Process Services
Business Logic: If Customer_Status = Gold Service_Fee = $8 else
Service_Fee = $20
Orchestration:
Fee database
DDA / Current Account
24.
25.
26. SOA basically delivers four types of service:
Functional Service: service for business applications.
Application Services: for deploying and developing applications.
Enterprise Services: for specifically implementing functionality.
Infrastructure Service: for nonfunctional purposes and can include
security and authentication.
27. Advantages of SOA
• Easy to integrate - is a service specification that provides implementation
transparency.
• Manage Complexity - the complexities get isolated, and integration becomes
more manageable.
• Platform Independence – It can communicate with other applications
through a common language.
• Loose coupling - It facilitates to implement services without impacting other
applications or services.
• Parallel Development -, it provides parallel development. As SOA follows
layer-based architecture
• The SOA services are easily available to any requester.
• Reliable - As services are small in size, it is easier to test and debug them.
28. Disadvantages
• It requires high investment cost (means large investment on
technology, development and human resource).
• There is greater overhead when a service interacts with another
service which increases the response time and machine load while
validating the input parameters.
• SOA is not suitable for GUI (graphical user interface) applications
which will become more complex when the SOA requires the heavy
data exchange.
29. What is a Monolithic Application?
•It is a software architecture where all components
and functionalities of an application are tightly
integrated into a single codebase, executed as a
single unit, and typically deployed as a single
application.
30. What is a Monolithic Application?
•it's an all-in-one approach where everything, including
the user interface, business logic, data access, and any
other necessary components, resides within a single
application stack.
31.
32. Monolithic application components
• Authorization: To give authorization to a user and allow them to use the
application.
• Presentation: To handle Hypertext Transfer Protocol requests and respond
with Extensible Markup Language or JavaScript Object Notation
• Business logic: The fundamental business logic that drives the
application’s functionality and features.
• Database Layer: Includes the data access object that accesses the
application’s database.
• Application Integration: Controls and manages the application’s
integration with other services or data sources.
35. Characteristics of Monolithic Applications
• Single Codebase: In a monolithic architecture, all parts of the application
share a single codebase. This makes it easy to manage and maintain because
there is no need to coordinate different code repositories.
• Tight Integration: Components in a monolithic application are tightly
integrated, enabling seamless communication and data sharing between
different parts of the application.
• Single Deployment: Monolithic applications are typically deployed as a single
unit, making it easier to manage deployment and scaling.
• Shared Resources: Components within the monolith share resources such as
memory and CPU, which can lead to efficient resource utilization.
• Simplified Development: Developing a monolithic application can be simpler
in the initial stages, as you don't need to deal with complex distributed
systems.
36. Advantages of Monolithic Applications
• Ease of Development
• Simplicity
• Debugging and Testing .
• Performance
• Cost-Effectiveness - For smaller projects or startups with limited
resources, monolithic applications can be cost-effective.
• The simplicity of development and deployment reduces the
operational overhead, allowing you to allocate resources more
efficiently.
37. Considerations and Challenges
• Scalability
• Maintenance: As monolithic applications become larger and more
complex, they can become harder to maintain and upgrade..
• Deployment: Rolling out updates to a monolithic application may
require downtime, impacting the user experience.
• Technology Stack: Choosing the right technology stack is critical in a
monolithic architecture. An improper choice can lead to bottlenecks
and performance issues.
• Team Size: The size and expertise of your development team should
align with the complexity of the monolithic application. Smaller teams
may find it easier to manage and maintain smaller monoliths.
40. When millions of users access an single application-
single instance – apply multiple VM/websites – move to
entire app ex: Amazon products – is high volume
Autoscaling-cloud
41. Microservices Architecture
• It is an architectural style that structures an application as a collection of
services that are:
• Independently deployable
• Loosely coupled
• Services are typically organized around business capabilities. Each service
is often owned by a single, small team.
• The microservice architecture enables an organization to deliver large,
complex applications rapidly, frequently, reliably and sustainably - a
necessity for competing and winning in today’s world.
42. Microservices Architecture
• Microservices allow a large application to be separated into smaller
independent parts, with each part having its own realm of
responsibility. To serve a single user request, a microservices-based
application can call on many internal microservices to compose its
response.
49. Difference
SOA. MSA.
It is a huge collection of services in which services
communicate with each other.
It is general architecture that takes large number of
services and break down into small services or
shareable component.
It is used to share the data storage. It has independent data storage.
It supports various multiple protocol. It supports HTTP/REST lightweight protocol.
In service oriented architecture, there is a multi-
threaded with more handle I/O.
In Micro service Architecture, there is single-
threaded with non-locking I/O handle.
It has common platform for all services.
It has platform like Nodejs is used and application
server not used.
It uses of container is less popular Docker linux. Its container work very well.
It uses traditional database. It uses non-relational database.
It uses ESB services for communication.
It does not use ESB services. It has a simple
messaging system.
It have common governance standard. Relaxed governance with more focus on people.
50. Data Duplication: Changing data at the primary source is one of the basic purposes of providing SOA for all applications. This
can reduce the necessity of maintaining complicated data synchronization patterns. Microservice applications usually have
local access to data. This, however, means there are sometimes duplications of data in the other systems, which can cause
complexity.
Data Storage: Microservices usually have individual data storage. SOA systems normally share data storage units.
Reusability: Reusing integrations is one of the primary goals of SOA. Reusing components in microservices throughout an
application can cause dependencies that limit resilience and agility.
Speed: Sharing a basic architecture can assist SOAs when simplifying troubleshooting and ongoing development. On the
other hand, SOAs may work more slowly, which limits sharing and favors duplication.
Communication: An SOA system provides each service a basic communication mechanism. This is an ESB (enterprise service
bus). This means a single point of failure can disrupt the entire enterprise. With microservice architecture, every service is
independent of one another.
Granularity: SOA exhibits a wide range of services. These can include small, specialty services to those that are enterprise-
wide. Microservices are all specialty. Programmers create each one to carry out one particular service extremely well.
Interoperability: SOAs are open to diverse messages and protocols. Microservices keep things simple and use messaging such
as HTTP/REST.
SOA vs. microservices
51. What are the Similarities?
Both are collections that focus on performing specific
functions.
Both are smaller in overall scope than one large monolithic
architecture.
Both require decentralization in the internal culture with cross-
functional collaborative abilities.
Both allow the choice of program languages that best suit
each service.
SOA and Microservices
52.
53.
54.
55. Examples of Microservices
• Amazon and Netflix, Uber - Amazon added more developers to work
on it, and the codebase became bigger. This made the architecture more complex
to modify, adding overheads to the process and slowing down the software
development lifecycle.
56. Which is Best for You?
• You would likely want an SOA if the answer is yes to the following questions:
• Do you have a large, diverse application environment?
• Do you want a system that can support multiple messaging protocols?
• Do you want a messaging system that works through an enterprise service bus?
• You would probably want microservices if the following apply to your organization:
• Do you have a smaller environment that doesn't require a strong communication layer?
• Do you need a system that provides extensive scalability?
• Do you want to build a smaller project with simpler messaging systems?
57. Examples of Microservices Frameworks for
Java
• Spring Boot. This is probably the best Java microservices framework that works on top of
languages for Inversion of Control, Aspect-Oriented Programming, and others.
• Jersey. This open-source framework supports JAX-RS APIs in Java and is very easy to use.
• Swagger. Helps you document API as well as gives you a development portal, which
allows users to test your APIs.
• Quarkus. This is a lightweight Java framework optimized for GraalVM and HotSpot, and
it’s tightly integrated with Kubernetes.
• Micronaut. It’s based on the Netty framework, which makes it well-suited for
microservices that need to handle a lot of traffic.
• Helidon. A microservices framework developed by Oracle. It is based on the MicroProfile
specification, making it interoperable with other MicroProfile-based frameworks.
• AxonIQ. A microservices framework designed for event-driven architectures. It provides
a comprehensive toolkit for building event-driven microservices, including a message
bus, event sourcing, and CQRS.
58. What do you mean by middleware?
• Middleware is software that different applications use to communicate
with each other.
• It provides functionality to connect applications intelligently and
efficiently so that you can innovate faster.
Example of middleware
• When you submit a form on a website, your computer sends the request in
XML or JSON to the web server. Then, the web server runs the business
logic based on the request, retrieves information from databases, or
communicates to other microservices using different protocols.
https://www.integrate.io/glossary/what-is-
middleware/#:~:text=APIs%20have%20become%20one%20of,access%20with%20a%20simple%20call.
59. What is DevOps in full?
• DevOps (a portmanteau of “development” and “operations”) is the
combination of practices and tools designed to increase an
organization's ability to deliver applications and services faster than
traditional software development processes.
• DevOps is a set of practices, tools, and a cultural philosophy that
automate and integrate the processes between software development
and IT teams.
• It emphasizes team empowerment, cross-team communication and
collaboration, and technology automation.
60. What is decoupling in API?
• provide a centralized place for new services to be created.
• a practice for reducing operational dependencies across different
systems
• A decoupled architecture is a broader design concept that aims to
minimize dependencies between components, while
microservices is a specific implementation of decoupling where a
system is divided into independent, smaller services.
61. Use case
In this use case, the insurance system has a sales database that
is automatically updated with the customer transaction details
after a monthly payment is made. The following illustration
shows how to build this system by using the decouple
messaging pattern.
The workflow consists of the following steps:
The frontend application calls the API Gateway with the payment information after a user makes their monthly payment.
The API Gateway runs the “Customer” Lambda function that saves the payment information in an Amazon Aurora database,
writes the transaction details in a message to the “Sales" Amazon SQS, and responds to the calling system with a success
message.
A “Sales” Lambda function pulls the transaction details from the SQS message and updates the sales data. Failure and retry
logic to update the sales database is incorporated as part of the “Sales” Lambda function.
All operations don’t need to be completed in
a single transaction, and some operations
can be asynchronous.