Event Driven Microservices architecture
Download as pptx, pdf1 like266 views
The document discusses the transition from monolithic architecture to event-driven microservices, highlighting the benefits of smaller codebases and autonomous teams. It addresses challenges related to distributed data, including consistency and querying, and introduces concepts such as domain-driven design, event sourcing, command query responsibility segregation, and sagas for maintaining data integrity. Ultimately, it emphasizes the importance of using event-driven architectures for achieving eventual consistency and facilitating faster innovation in software development.
1 of 29
Download to read offline
Ad
Recommended
Event-Driven Architecture (EDA)
Event-Driven Architecture (EDA)WSO2 The document discusses Event Driven Architecture (EDA) and its application in enterprise systems, specifically in a healthcare scenario. It outlines key components of EDA such as event generators, consumers, and channels, and highlights the benefits of using EDA for modularity, asynchronous communication, and real-time event processing. Additionally, it addresses potential challenges in adopting EDA and describes how WSO2 products support these architectures.
Event-driven microservices
Event-driven microservicesAndrew Schofield 1) Event-driven microservices involve microservices communicating primarily through events published to an event backbone. This loosely couples microservices and allows for eventual data consistency.
2) Apache Kafka is an open-source streaming platform that can be used to build an event backbone, allowing microservices to reliably publish and subscribe to events. It supports streaming, storage, and processing of event data.
3) Common patterns for event-driven microservices include database per service for independent data ownership, sagas for coordinated multi-step processes, event sourcing to capture all state changes, and CQRS to separate reads from writes.
Micro services Architecture
Micro services ArchitectureAraf Karsh Hamid The document provides an overview of microservices architecture. It discusses key characteristics of microservices such as each service focusing on a specific business capability, decentralized governance and data management, and infrastructure automation. It also compares microservices to monolithic and SOA architectures. Some design styles enabled by microservices like domain-driven design, event sourcing, and functional reactive programming are also covered at a high level. The document aims to introduce attendees to microservices concepts and architectures.
Introduction to Microservices
Introduction to MicroservicesMahmoudZidan41 The document discusses the microservices architectural style, detailing its advantages and challenges compared to monolithic applications. It emphasizes the importance of domain-driven design, independent deployment, and communication between services while highlighting issues such as data consistency and service integration. Additionally, it covers elements like monitoring, deployment strategies, and the technical concerns associated with implementing microservices.
Microservice vs. Monolithic Architecture
Microservice vs. Monolithic ArchitecturePaul Mooney The document compares the benefits and drawbacks of microservice architecture versus monolithic architecture, highlighting that microservices offer enhanced flexibility, scalability, and reduced dependencies. It outlines the anatomy of a microservice, emphasizing the decoupled middleware design and centralized service bus. Additionally, it raises various questions related to continuous integration, monitoring, and deployment strategies in a microservice environment.
Event driven architecture
Event driven architectureShadrach Jabonir The document discusses event-driven architecture (EDA). EDA is a software architecture pattern that promotes processing, detecting, consuming, and reacting to events. An event is defined as a significant change in state. EDA allows for real-time processing as events happen, push notifications, and immediate actions by consumers without waiting. EDA is scalable in processing, design, and adapting to change. It focuses on domain logic and collaborating with domain experts. EDA uses message brokers, producers that generate events, and consumers that process events.
Introduction to Microservices
Introduction to MicroservicesRoger van de Kimmenade The document provides an overview of microservices architecture including:
- Definitions and characteristics of microservices such as componentization via services, decentralized governance, and infrastructure automation.
- Common drivers for adopting microservices like agility, safety, and scalability.
- Guidelines for decomposing monolithic applications into microservices based on business capabilities and domain-driven design.
- Discussion of differences between microservices and service-oriented architecture (SOA).
- Ecosystem of tools involved in microservices including development frameworks, APIs, databases, containers, and service meshes.
- Common design patterns and anti-patterns when developing microservices.
Microservice Architecture
Microservice Architecturetyrantbrian The document provides an extensive overview of microservice architecture, defining it as an approach where applications are developed as suites of small, independently deployable services that communicate over lightweight mechanisms. It discusses the evolution of this architecture from monolithic and layered systems to a more decentralized governance and data management approach, emphasizing benefits such as better scalability, maintainability, and the choice of technology stacks. Key features include autonomous teams, smart endpoint interactions, and a focus on continuous delivery and resilience in software development.
Windows Azure Service Bus
Windows Azure Service BusReturn on Intelligence This document provides an overview of Windows Azure Service Bus and its key components:
- Service Bus allows one-directional communication via queues that store messages until received and topics that use subscriptions to filter messages. It also enables bi-directional communication via relays.
- Service Bus queues are used for communication between applications like web and worker roles or on-premises and cloud apps.
- Topics and subscriptions provide one-to-many communication using a publish/subscribe pattern with optional filtering of messages for each subscription.
- The Service Bus relay enables hybrid apps that run in Azure and on-premises without requiring firewall configuration changes.
Microservices
MicroservicesSmartBear The document provides an overview of microservices architecture, highlighting its advantages such as ease of deployment, separation of services, and improved fault isolation. It also discusses challenges related to complexity, testing, and performance in microservices environments, along with strategies to address these issues, including definition-driven development and continuous monitoring. Additionally, the document introduces SmartBear's API lifecycle toolset designed to enhance the development, testing, and monitoring of microservices.
Introduction to microservices
Introduction to microservicesPaulo Gandra de Sousa This document provides an introduction to microservices, including:
- Microservices are small, independently deployable services that work together and are modeled around business domains.
- They allow for independent scaling, technology diversity, and enable resiliency through failure design.
- Implementing microservices requires automation, high cohesion, loose coupling, and stable APIs. Identifying service boundaries and designing for orchestration and data management are also important aspects of microservices design.
- Microservices are not an end goal but a means to solve problems of scale; they must be adopted judiciously based on an organization's needs.
Microservices Architecture - Cloud Native Apps
Microservices Architecture - Cloud Native AppsAraf Karsh Hamid This document provides an overview of microservices architecture, including concepts, characteristics, infrastructure patterns, and software design patterns relevant to microservices. It discusses when microservices should be used versus monolithic architectures, considerations for sizing microservices, and examples of pioneers in microservices implementation like Netflix and Spotify. The document also covers domain-driven design concepts like bounded context that are useful for decomposing monolithic applications into microservices.
Microservice Architecture | Microservices Tutorial for Beginners | Microservi...
Microservice Architecture | Microservices Tutorial for Beginners | Microservi...Edureka! The document discusses the differences between monolithic and microservices architectures, highlighting challenges such as reduced agility, scalability issues, and fault tolerance in monolithic systems. It uses Uber's transition from a monolithic structure to a microservices architecture as a key example, emphasizing the benefits of decoupled components and independent deployment. Best practices for designing microservices are also outlined, including the use of separate data stores and treating servers as stateless.
Event Driven Architecture
Event Driven ArchitectureStefan Norberg The document discusses domain event-driven architecture (EDA) as a solution to the challenges presented by traditional service-oriented architecture (SOA). It highlights the principles, benefits, and implementation strategies for EDA, emphasizing real-time event processing and the reduction of points of integration. The author also provides examples from Unibet's experience with EDA and outlines the technological requirements for implementing such systems.
Event Driven Software Architecture Pattern
Event Driven Software Architecture Patternjeetendra mandal An event-driven architecture consists of event producers that generate event streams and event consumers that listen for events. It allows for loose coupling between components and asynchronous event handling. Key aspects include publish/subscribe messaging patterns, event processing by middleware, and real-time or near real-time information flow. Benefits include scalability, loose coupling, fault tolerance, and the ability to add new consumers easily. Challenges include guaranteed delivery, processing events in order or exactly once across multiple consumer instances. Common tools used include Apache Kafka, Apache ActiveMQ, Redis, and Apache Pulsar.
Microservice Architecture Patterns, by Richard Langlois P. Eng.
Microservice Architecture Patterns, by Richard Langlois P. Eng.Richard Langlois P. Eng. This document outlines various patterns and principles of microservice architecture, emphasizing its structure as a set of loosely coupled services that implement business capabilities. It covers aspects such as core patterns, decomposition, deployment strategies, cross-cutting concerns, communication styles, external APIs, and service discovery methods. The overall objective is to enhance software development through continuous delivery and to provide a framework for effectively managing microservices.
Microservice architecture design principles
Microservice architecture design principlesSanjoy Kumar Roy - Microservices advocate creating a system from small, isolated services that each own their data and are independently scalable and resilient. They are inspired by biological cells that are small, single-purpose, and work together through messaging.
- The system is divided using a divide and conquer approach, decomposing it into discrete subsystems that communicate over well-defined protocols. Each microservice focuses on a single business capability and owns its own data and behavior.
- Microservices communicate asynchronously through APIs and events to maintain independence and isolation, which enables continuous delivery, failure resilience, and independent scaling of each service.
Event Driven Architecture
Event Driven ArchitectureChris Patterson Chris Patterson presented on event driven architecture. He introduced event driven architecture as a method where events flow between decoupled components and services. He defined events as representations of changes in state that are self-contained and identified. Events can be business events related to real world occurrences, lifecycle events for processes and states, or management events related to time and limits. The presentation discussed how events are published and consumed asynchronously between independent components using messaging systems like MassTransit. Commands were also introduced as messages telling components to perform actions.
Event driven microservices
Event driven microservicesAnthony Martin Event-driven microservices communicate asynchronously using events published to an event backbone like Apache Kafka. This approach offers benefits like loose coupling, responsiveness, and independent scalability. Various patterns can be used to manage complexity, including having each service store its own data, using Kafka log compaction to replicate data across services, orchestrating multi-step processes through sagas, and separating read and write concerns with CQRS. Event storming helps identify the events, actors, and data in an application to structure it in an event-driven way.
IBM MQ - High Availability and Disaster Recovery
IBM MQ - High Availability and Disaster RecoveryMarkTaylorIBM IBM MQ provides capabilities to keep data safe and businesses running in the event of failures. This includes solutions for high availability (HA) and disaster recovery (DR) whether running on-premises or in hybrid cloud environments. HA aims to keep systems running through failures while DR focuses on recovering after an HA failure. Key HA technologies in IBM MQ include queue manager clusters, queue sharing groups, multi-instance queue managers, and HA clusters. These solutions provide redundancy to prevent single points of failure and enable fast failover. DR requires replicating data to separate sites which IBM MQ supports through various backup and replication features.
Introduction To Microservices
Introduction To MicroservicesLalit Kale The document is a presentation on microservices by Lalit Kale, covering their significance in business transformation, scalability, and agility. It elaborates on the architectural style of microservices, principles for designing and deploying them, and contrasts microservices with monolithic architectures. Additionally, it discusses considerations for interactions, deployment, and scaling within microservices ecosystems.
Introduction to Microservices Patterns
Introduction to Microservices PatternsDimosthenis Botsaris The document provides an overview of microservices and monolithic application architectures, detailing their types, advantages, and disadvantages. It discusses challenges associated with microservices, such as data ownership, inter-process communication, and ensuring data consistency in distributed systems. It also covers various patterns for implementing microservices, including API gateways, event-driven architectures, and transaction management strategies like sagas and the outbox pattern.
Event Driven Architecture (EDA) Reference Architecture
Event Driven Architecture (EDA) Reference ArchitectureBob Rhubart The document discusses Oracle's approach to event driven architecture (EDA). It provides an overview of EDA and the business drivers for adopting an EDA approach. It then details Oracle's EDA reference architecture, including the conceptual view, logical view, product mapping, and deployment view. The reference architecture provides guidance on developing EDA solutions using Oracle products.
Why a Multi-cloud Strategy is Essential
Why a Multi-cloud Strategy is EssentialAlibaba Cloud The document discusses the importance of a multi-cloud strategy, highlighting the need for vendor independence, regulatory compliance, and global service availability to avoid vendor lock-in and take advantage of diverse services. It outlines various multi-cloud use cases such as disaster recovery, hybrid cloud configurations, and service distribution, emphasizing interoperability and optimized management across multiple cloud providers. Additionally, it presents Alibaba Cloud’s offerings to support a multi-cloud approach, including cross-cloud connectivity, operational integrations, and tools for data management.
What are Microservices | Microservices Architecture Training | Microservices ...
What are Microservices | Microservices Architecture Training | Microservices ...Edureka! The document discusses microservice architecture, explaining its advantages over monolithic architecture, which is often complex and unscalable. It outlines the characteristics of microservices, such as being small, focused, and loosely coupled, and highlights features like independent deployment and fault isolation. Additionally, it mentions companies that are adopting microservices for their applications.
App Modernization Pitch Deck.pptx
App Modernization Pitch Deck.pptxMONISH407209 This document provides an overview of modernizing enterprise applications with Azure Platform-as-a-Service (PaaS). It discusses reasons why businesses modernize like reducing technical debt and optimizing costs. It also covers challenges of modernization like fragmented security and conflicting priorities. The document then presents different approaches to application migration and modernization on Azure including migrating to IaaS, replacing with SaaS, staying on-premises but connected to cloud, and modernizing directly on PaaS. Key benefits of a successful modernization are also listed like prioritizing security, resilience, and performance as well as innovating faster. The document concludes with case studies of companies successfully modernizing applications on Azure.
Event Driven Architecture (EDA) Reference Architecture | Anbu Krishnaswamy
Event Driven Architecture (EDA) Reference Architecture | Anbu KrishnaswamyBob Rhubart This document summarizes Oracle's approach to event driven architecture (EDA). It discusses EDA drivers and adoption approaches, including using an EDA maturity model and roadmap planning. It then presents Oracle's EDA reference architecture, including conceptual, logical, and deployment views. The reference architecture maps Oracle products to the EDA framework and is intended to help customers accelerate EDA adoption.
Infrastructure as Code
Infrastructure as CodeRobert Greiner The document discusses the integration of development and operations through infrastructure as code to enhance application development processes. It emphasizes continuous integration, automation, and collaboration between developers and operations teams using tools like AWS CloudFormation and CodeDeploy. The content also outlines a challenge for creating automated AWS environments and highlights the benefits of automation in modern development workflows.
Service Mesh CTO Forum (Draft 3)
Service Mesh CTO Forum (Draft 3)Rick Hightower The document discusses the evolution and architecture of microservices, emphasizing the importance of service mesh in managing complexity and enhancing security within microservice environments. It outlines key components and functions of service meshes, including observability, traffic management, and security protocols like zero trust networking. Additionally, it highlights various microservice patterns, deployment strategies, and the integration of continuous delivery and DevOps practices to optimize the development lifecycle.
Iot cloud service v2.0
Iot cloud service v2.0Vinod Wilson The document discusses transitioning from a monolithic architecture to microservices architecture for an IoT cloud platform. Some key points include:
- The goals of enabling scalability, supporting new markets, and innovation.
- Moving to a microservices architecture can help with scalability, fault tolerance, and independent deployability compared to a monolith.
- Organizational structure should also transition from function-based to product-based to align with the architecture.
- Technical considerations in building microservices include service interfaces, data management, fault tolerance, and DevOps practices.
More Related Content
What's hot (20)
Windows Azure Service Bus
Windows Azure Service BusReturn on Intelligence This document provides an overview of Windows Azure Service Bus and its key components:
- Service Bus allows one-directional communication via queues that store messages until received and topics that use subscriptions to filter messages. It also enables bi-directional communication via relays.
- Service Bus queues are used for communication between applications like web and worker roles or on-premises and cloud apps.
- Topics and subscriptions provide one-to-many communication using a publish/subscribe pattern with optional filtering of messages for each subscription.
- The Service Bus relay enables hybrid apps that run in Azure and on-premises without requiring firewall configuration changes.
Microservices
MicroservicesSmartBear The document provides an overview of microservices architecture, highlighting its advantages such as ease of deployment, separation of services, and improved fault isolation. It also discusses challenges related to complexity, testing, and performance in microservices environments, along with strategies to address these issues, including definition-driven development and continuous monitoring. Additionally, the document introduces SmartBear's API lifecycle toolset designed to enhance the development, testing, and monitoring of microservices.
Introduction to microservices
Introduction to microservicesPaulo Gandra de Sousa This document provides an introduction to microservices, including:
- Microservices are small, independently deployable services that work together and are modeled around business domains.
- They allow for independent scaling, technology diversity, and enable resiliency through failure design.
- Implementing microservices requires automation, high cohesion, loose coupling, and stable APIs. Identifying service boundaries and designing for orchestration and data management are also important aspects of microservices design.
- Microservices are not an end goal but a means to solve problems of scale; they must be adopted judiciously based on an organization's needs.
Microservices Architecture - Cloud Native Apps
Microservices Architecture - Cloud Native AppsAraf Karsh Hamid This document provides an overview of microservices architecture, including concepts, characteristics, infrastructure patterns, and software design patterns relevant to microservices. It discusses when microservices should be used versus monolithic architectures, considerations for sizing microservices, and examples of pioneers in microservices implementation like Netflix and Spotify. The document also covers domain-driven design concepts like bounded context that are useful for decomposing monolithic applications into microservices.
Microservice Architecture | Microservices Tutorial for Beginners | Microservi...
Microservice Architecture | Microservices Tutorial for Beginners | Microservi...Edureka! The document discusses the differences between monolithic and microservices architectures, highlighting challenges such as reduced agility, scalability issues, and fault tolerance in monolithic systems. It uses Uber's transition from a monolithic structure to a microservices architecture as a key example, emphasizing the benefits of decoupled components and independent deployment. Best practices for designing microservices are also outlined, including the use of separate data stores and treating servers as stateless.
Event Driven Architecture
Event Driven ArchitectureStefan Norberg The document discusses domain event-driven architecture (EDA) as a solution to the challenges presented by traditional service-oriented architecture (SOA). It highlights the principles, benefits, and implementation strategies for EDA, emphasizing real-time event processing and the reduction of points of integration. The author also provides examples from Unibet's experience with EDA and outlines the technological requirements for implementing such systems.
Event Driven Software Architecture Pattern
Event Driven Software Architecture Patternjeetendra mandal An event-driven architecture consists of event producers that generate event streams and event consumers that listen for events. It allows for loose coupling between components and asynchronous event handling. Key aspects include publish/subscribe messaging patterns, event processing by middleware, and real-time or near real-time information flow. Benefits include scalability, loose coupling, fault tolerance, and the ability to add new consumers easily. Challenges include guaranteed delivery, processing events in order or exactly once across multiple consumer instances. Common tools used include Apache Kafka, Apache ActiveMQ, Redis, and Apache Pulsar.
Microservice Architecture Patterns, by Richard Langlois P. Eng.
Microservice Architecture Patterns, by Richard Langlois P. Eng.Richard Langlois P. Eng. This document outlines various patterns and principles of microservice architecture, emphasizing its structure as a set of loosely coupled services that implement business capabilities. It covers aspects such as core patterns, decomposition, deployment strategies, cross-cutting concerns, communication styles, external APIs, and service discovery methods. The overall objective is to enhance software development through continuous delivery and to provide a framework for effectively managing microservices.
Microservice architecture design principles
Microservice architecture design principlesSanjoy Kumar Roy - Microservices advocate creating a system from small, isolated services that each own their data and are independently scalable and resilient. They are inspired by biological cells that are small, single-purpose, and work together through messaging.
- The system is divided using a divide and conquer approach, decomposing it into discrete subsystems that communicate over well-defined protocols. Each microservice focuses on a single business capability and owns its own data and behavior.
- Microservices communicate asynchronously through APIs and events to maintain independence and isolation, which enables continuous delivery, failure resilience, and independent scaling of each service.
Event Driven Architecture
Event Driven ArchitectureChris Patterson Chris Patterson presented on event driven architecture. He introduced event driven architecture as a method where events flow between decoupled components and services. He defined events as representations of changes in state that are self-contained and identified. Events can be business events related to real world occurrences, lifecycle events for processes and states, or management events related to time and limits. The presentation discussed how events are published and consumed asynchronously between independent components using messaging systems like MassTransit. Commands were also introduced as messages telling components to perform actions.
Event driven microservices
Event driven microservicesAnthony Martin Event-driven microservices communicate asynchronously using events published to an event backbone like Apache Kafka. This approach offers benefits like loose coupling, responsiveness, and independent scalability. Various patterns can be used to manage complexity, including having each service store its own data, using Kafka log compaction to replicate data across services, orchestrating multi-step processes through sagas, and separating read and write concerns with CQRS. Event storming helps identify the events, actors, and data in an application to structure it in an event-driven way.
IBM MQ - High Availability and Disaster Recovery
IBM MQ - High Availability and Disaster RecoveryMarkTaylorIBM IBM MQ provides capabilities to keep data safe and businesses running in the event of failures. This includes solutions for high availability (HA) and disaster recovery (DR) whether running on-premises or in hybrid cloud environments. HA aims to keep systems running through failures while DR focuses on recovering after an HA failure. Key HA technologies in IBM MQ include queue manager clusters, queue sharing groups, multi-instance queue managers, and HA clusters. These solutions provide redundancy to prevent single points of failure and enable fast failover. DR requires replicating data to separate sites which IBM MQ supports through various backup and replication features.
Introduction To Microservices
Introduction To MicroservicesLalit Kale The document is a presentation on microservices by Lalit Kale, covering their significance in business transformation, scalability, and agility. It elaborates on the architectural style of microservices, principles for designing and deploying them, and contrasts microservices with monolithic architectures. Additionally, it discusses considerations for interactions, deployment, and scaling within microservices ecosystems.
Introduction to Microservices Patterns
Introduction to Microservices PatternsDimosthenis Botsaris The document provides an overview of microservices and monolithic application architectures, detailing their types, advantages, and disadvantages. It discusses challenges associated with microservices, such as data ownership, inter-process communication, and ensuring data consistency in distributed systems. It also covers various patterns for implementing microservices, including API gateways, event-driven architectures, and transaction management strategies like sagas and the outbox pattern.
Event Driven Architecture (EDA) Reference Architecture
Event Driven Architecture (EDA) Reference ArchitectureBob Rhubart The document discusses Oracle's approach to event driven architecture (EDA). It provides an overview of EDA and the business drivers for adopting an EDA approach. It then details Oracle's EDA reference architecture, including the conceptual view, logical view, product mapping, and deployment view. The reference architecture provides guidance on developing EDA solutions using Oracle products.
Why a Multi-cloud Strategy is Essential
Why a Multi-cloud Strategy is EssentialAlibaba Cloud The document discusses the importance of a multi-cloud strategy, highlighting the need for vendor independence, regulatory compliance, and global service availability to avoid vendor lock-in and take advantage of diverse services. It outlines various multi-cloud use cases such as disaster recovery, hybrid cloud configurations, and service distribution, emphasizing interoperability and optimized management across multiple cloud providers. Additionally, it presents Alibaba Cloud’s offerings to support a multi-cloud approach, including cross-cloud connectivity, operational integrations, and tools for data management.
What are Microservices | Microservices Architecture Training | Microservices ...
What are Microservices | Microservices Architecture Training | Microservices ...Edureka! The document discusses microservice architecture, explaining its advantages over monolithic architecture, which is often complex and unscalable. It outlines the characteristics of microservices, such as being small, focused, and loosely coupled, and highlights features like independent deployment and fault isolation. Additionally, it mentions companies that are adopting microservices for their applications.
App Modernization Pitch Deck.pptx
App Modernization Pitch Deck.pptxMONISH407209 This document provides an overview of modernizing enterprise applications with Azure Platform-as-a-Service (PaaS). It discusses reasons why businesses modernize like reducing technical debt and optimizing costs. It also covers challenges of modernization like fragmented security and conflicting priorities. The document then presents different approaches to application migration and modernization on Azure including migrating to IaaS, replacing with SaaS, staying on-premises but connected to cloud, and modernizing directly on PaaS. Key benefits of a successful modernization are also listed like prioritizing security, resilience, and performance as well as innovating faster. The document concludes with case studies of companies successfully modernizing applications on Azure.
Event Driven Architecture (EDA) Reference Architecture | Anbu Krishnaswamy
Event Driven Architecture (EDA) Reference Architecture | Anbu KrishnaswamyBob Rhubart This document summarizes Oracle's approach to event driven architecture (EDA). It discusses EDA drivers and adoption approaches, including using an EDA maturity model and roadmap planning. It then presents Oracle's EDA reference architecture, including conceptual, logical, and deployment views. The reference architecture maps Oracle products to the EDA framework and is intended to help customers accelerate EDA adoption.
Infrastructure as Code
Infrastructure as CodeRobert Greiner The document discusses the integration of development and operations through infrastructure as code to enhance application development processes. It emphasizes continuous integration, automation, and collaboration between developers and operations teams using tools like AWS CloudFormation and CodeDeploy. The content also outlines a challenge for creating automated AWS environments and highlights the benefits of automation in modern development workflows.
Similar to Event Driven Microservices architecture (20)
Service Mesh CTO Forum (Draft 3)
Service Mesh CTO Forum (Draft 3)Rick Hightower The document discusses the evolution and architecture of microservices, emphasizing the importance of service mesh in managing complexity and enhancing security within microservice environments. It outlines key components and functions of service meshes, including observability, traffic management, and security protocols like zero trust networking. Additionally, it highlights various microservice patterns, deployment strategies, and the integration of continuous delivery and DevOps practices to optimize the development lifecycle.
Iot cloud service v2.0
Iot cloud service v2.0Vinod Wilson The document discusses transitioning from a monolithic architecture to microservices architecture for an IoT cloud platform. Some key points include:
- The goals of enabling scalability, supporting new markets, and innovation.
- Moving to a microservices architecture can help with scalability, fault tolerance, and independent deployability compared to a monolith.
- Organizational structure should also transition from function-based to product-based to align with the architecture.
- Technical considerations in building microservices include service interfaces, data management, fault tolerance, and DevOps practices.
Microservices in Action
Microservices in ActionBhagwat Kumar The document discusses microservices architecture, contrasting it with traditional monolithic architecture, highlighting the benefits and challenges of microservices including independent deployment and operational complexity. It covers characteristics like decentralized governance and fault isolation, and introduces tools like Spring Cloud and Netflix OSS for managing microservices. Additionally, it addresses misconceptions in distributed computing and provides references for further reading.
Get the Message Across: Seamlessly Transport Data to Apps, Anywhere
Get the Message Across: Seamlessly Transport Data to Apps, AnywhereVMware Tanzu This document discusses how Pivotal Cloud Foundry and Solace can be used together to seamlessly transport data between applications across distributed environments. It notes that Pivotal Cloud Foundry provides capabilities like elastic scaling and automation, while Solace provides an event mesh to enable event-driven communication between applications on Cloud Foundry, legacy systems, IoT devices, and across public and private clouds. A case study is presented of how a global bank used Pivotal Cloud Foundry and Solace to build a fault-tolerant global hybrid cloud data fabric and enable new applications to integrate with legacy systems.
Concurrency at Scale: Evolution to Micro-Services
Concurrency at Scale: Evolution to Micro-ServicesRandy Shoup The document discusses the evolution from monolithic architectures to microservices, emphasizing the benefits and challenges of both approaches. It highlights the importance of reactive microservices that enhance responsiveness, resilience, elasticity, and message-driven communication. Additionally, it outlines strategies for migrating to microservices, including incremental changes, team organization, and the use of frameworks and tools to simplify the process.
The Need of Cloud-Native Application
The Need of Cloud-Native ApplicationEmiliano Pecis The document discusses the need for cloud-native applications using microservices, containers, and DevOps to improve time to market, scalability, and system resilience. It contrasts microservices with monolithic architectures, emphasizing the benefits of decentralized data management and service orchestration. Key components such as API gateways, service discovery, and circuit breakers are highlighted as essential for managing cloud-native application lifecycles.
Do I Need A Service Mesh.pptx
Do I Need A Service Mesh.pptxPINGXIONG3 This document discusses when a service mesh may be needed and provides an overview of the current service mesh landscape. It begins with why microservices are adopted and the challenges of operating distributed applications. It then describes a maturity journey where a service mesh is not initially needed but may become useful for applications that become more complex, distributed, and interdependent. The document outlines some current major service mesh implementations and notes that the technology is still new and changing rapidly. It recommends investigating service meshes through proof of concepts but cautions that production usage requires significant resources. It profiles F5 Aspen Mesh and NGINX solutions for service meshes and microservices.
Service Mesh Talk for CTO Forum
Service Mesh Talk for CTO ForumRick Hightower The document discusses the architecture and evolution of service meshes in microservices, emphasizing their crucial role in managing complexities like service discovery, routing, and security. It highlights the benefits of adopting microservices along with CI/CD practices to achieve faster and more efficient software delivery. Additionally, it outlines various patterns and best practices for implementing microservices and service meshes, including observability and traffic management strategies.
Microservices session 1
Microservices session 1Shouri Varanasi This document discusses microservices architecture and compares it to monolithic architecture. It begins by outlining the agenda and then defines prominent design philosophies like OOP, MVC, and concepts like cohesion and coupling. It then provides definitions and comparisons of monolithic vs microservices approaches. Key differences are that microservices have separate processes, independent deployability, and allow for different programming languages. The document discusses integration patterns for microservices like synchronous vs asynchronous communication using REST and message queues. Other topics covered include service versioning, orchestration vs choreography for business processes, and best practices for monitoring, logging and third party integration. Finally an example microservices architecture for a Cloud Foundation application is presented.
Redis and Kafka - Simplifying Advanced Design Patterns within Microservices A...
Redis and Kafka - Simplifying Advanced Design Patterns within Microservices A...HostedbyConfluent The document discusses advanced microservices design patterns, focusing on how to effectively utilize Kafka and Redis in microservices architectures. Key concepts include characteristics of microservices, the challenges of data management, and various design patterns like event sourcing and CQRS. It also highlights the need for improved communication and collaboration within teams to enhance time-to-market.
Redis and Kafka - Advanced Microservices Design Patterns Simplified
Redis and Kafka - Advanced Microservices Design Patterns SimplifiedAllen Terleto The document discusses advanced design patterns in microservices architecture, specifically through the lens of Redis and Kafka technologies. It emphasizes the challenges of communication, data management, and autonomy among microservices while offering solutions such as event sourcing and CQRS. The presentation outlines various design patterns and their benefits in managing microservices complexity, supported by practical resources and examples.
apidays LIVE Jakarta - Building an Event-Driven Architecture by Harin Honesty...
apidays LIVE Jakarta - Building an Event-Driven Architecture by Harin Honesty...apidays The document discusses Event-Driven Architecture (EDA), highlighting its benefits such as improved agility, real-time processing, and scalability compared to traditional monolithic and API-driven architectures. It also introduces Solace PubSub+, an event streaming and management platform, detailing its deployment options and key features like event mesh for dynamic event routing. Finally, it outlines scenarios for choosing EDA over REST, emphasizing its capabilities in handling high volumes and velocities of data.
Patterns of Distributed Application Design
Patterns of Distributed Application DesignGlobalLogic Ukraine The document discusses various patterns and concepts in distributed application design, focusing on scalability, service architecture, and data consistency. Key topics include service-oriented approaches, microservices, high availability, authentication, and different communication methods between services. It also highlights the importance of load balancing, service discovery, and eventual consistency in modern software architectures.
Cloud Application architecture styles
Cloud Application architecture styles Nilay Shrivastava The document outlines seven cloud application architecture styles, including n-tier, web-queue-worker, microservices, CQRS, event-driven, big data, and big compute architectures. Each architecture is described with its appropriate use cases, benefits, and challenges. Understanding these architectures is essential for effective cloud application deployment and management.
Building data-driven microservices
Building data-driven microservicesStreamlio The document discusses the concept of microservices, highlighting the differences between monolithic and microservices architectures, including the benefits and challenges of each. It outlines various approaches to designing microservices, focusing on how they can operate independently and communicate via different protocols, while also introducing Streamlio's technology for managing microservices efficiently. Additionally, it presents various pros and cons of different service connection strategies, emphasizing the importance of orchestration, messaging, and storage in building data-driven microservices.
Microservice intro
Microservice introramesh_sharma This document provides an overview of microservices and monolithic architectures. It discusses how monolithic applications are self-contained and execute end-to-end tasks, while microservices are small, independent services that communicate to perform tasks. The document outlines characteristics of each approach and compares their advantages and disadvantages, such as improved scalability, deployment and innovation with microservices versus better performance with monolithic architectures. Examples of companies using microservices are also provided.
Tokyo Azure Meetup #5 - Microservices and Azure Service Fabric
Tokyo Azure Meetup #5 - Microservices and Azure Service FabricTokyo Azure Meetup The document discusses building microservice-based applications using Azure Service Fabric, highlighting benefits such as scalability, agility, and improved resource utilization. It outlines the characteristics and principles of microservices, challenges faced in their implementation, and the capabilities of Azure Service Fabric, including management, deployment, and operational support for both stateless and stateful services. Additionally, it emphasizes the advantages of containerization and the importance of DevOps practices in maintaining microservices architectures.
Alex Thissen (Xpirit) - Een verschuiving in architectuur: op weg naar microse...
Alex Thissen (Xpirit) - Een verschuiving in architectuur: op weg naar microse...AFAS Software This document discusses microservices architecture as a modern approach to application development. It begins by outlining some of the challenges with monolithic architectures and how microservices address needs for scalability, agility, availability and efficiency. Key characteristics of microservices are that they are independently deployable, use lightweight protocols for communication, and are organized around business capabilities rather than technical boundaries. The document provides examples of how to decompose a monolithic application into microservices and discusses considerations for designing services, service communication, and hosting microservices using containers and orchestration platforms.
Database@Home : Data Driven Apps - Data-driven Microservices Architecture wit...
Database@Home : Data Driven Apps - Data-driven Microservices Architecture wit...Tammy Bednar The document outlines the architecture and challenges of data-driven microservices utilizing Oracle's converged database, Kubernetes, and Helidon on Oracle Cloud. It discusses key components such as data management, microservices frameworks, event sourcing, and the saga pattern for distributed transactions. Additionally, it addresses real-world challenges faced in DevOps environments regarding authentication, data privacy, and the onboarding of IT products.
BlockChain-1.pptx
BlockChain-1.pptxHussainPashaShaik1 The document provides an overview of blockchain fundamentals and Hyperledger. It discusses the origins of blockchain technology in the Bitcoin whitepaper and how it aimed to solve problems with digital currencies like double spending. It then summarizes key aspects of blockchain like decentralization, distributed ledgers, blocks and hashes. The document also provides a high-level introduction to Hyperledger Fabric, including that it is an enterprise-grade distributed ledger platform focused on performance and confidentiality. It discusses some of the main components of Hyperledger Fabric like peers, ordering service and channels.
Ad
Recently uploaded (20)
ElysiumPro Company Profile 2025-2026.pdf
ElysiumPro Company Profile 2025-2026.pdfinfo751436 Description
ElysiumPro | IEEE Final Year Projects | Best Internship Training | Inplant Training in Madurai
Best Final Year project training center
Address:
First Floor, A Block, 'Elysium Campus, 229, Church Rd, Vaigai Colony, Madurai, Tamil Nadu 625020
Plus Code:
W4CX+56 Madurai, Tamil Nadu
+91 9944793398
[email protected]
Elysium Group of Companies established ElysiumPro in 2001. Since its inception, it has been the most sought-after destination for final year project development and research papers among the students. Our commitment to providing quality project training & documentation to students has always been exceptional. We deliver the final year engineering projects and technical documents that provide extra edge and industry exposure to land prestigious jobs and reputed institutions for higher studies. Students from all over the country avail of our services for their final year projects. On average, we develop 5000+ projects and research papers per year on varied advanced domains. Python, JAVA, PHP, Android, Matlab, LabView, VLSI, SIMULINK, Power electronics, Power System, Antenna, Machine Learning, Deep Learning, Data Science, Artificial Intelligence, data Mining, Big Data, Cloud Computing, IoT,
Hours of Operation: -
Sunday 10am-1pm
Monday 7.30am-8pm
Tuesday 7.30am-8pm
Wednesday 7.30am-8pm
Thursday 7.30am-8pm
Friday 7.30am-8pm
Saturday 7.30am-8pm
Web Site:
https://elysiumpro.in/
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Youtube Geotagged Video:
https://youtu.be/QULY6XfuMyo
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Slideshow Images (Google Photos):
https://photos.app.goo.gl/hVwQJtkeptA1JZKd9
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
GBP Listing:
https://goo.gl/maps/6d6hko6TsDYyeDrz9
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Serving Areas:
https://www.google.com/maps/d/edit?mid=1-fsZogBiEAcjGP_aDyI0UKKIcwVUWfo&usp=sharing
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Google Site:
https://elysiumpro-project-center.business.site
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Google Sheet: https://docs.google.com/spreadsheets/d/1uXA07zxrUx2FCnBZWH80PpBZQrrX-2q1UBBe_0k3Yeo
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Google Document: https://docs.google.com/document/d/1BU4ZHW_41XJm2lvTq9pWYUpZILAEmF9dWEw7-DBbWoE
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Google Slides: https://docs.google.com/presentation/d/1uF8q6ueJWcAnhKTQsZxLE0Bo9PwgRNwCeuGV_ZgbSyU
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Machine Learning - Classification Algorithms
Machine Learning - Classification Algorithmsresming1 This covers traditional machine learning algorithms for classification. It includes Support vector machines, decision trees, Naive Bayes classifier , neural networks, etc.
It also discusses about model evaluation and selection. It discusses ID3 and C4.5 algorithms. It also describes k-nearest neighbor classifer.
Fundamentals of Digital Design_Class_21st May - Copy.pptx
Fundamentals of Digital Design_Class_21st May - Copy.pptxdrdebarshi1993 Basics of Number Systems and Logic Gates
FUNDAMENTALS OF COMPUTER ORGANIZATION AND ARCHITECTURE
FUNDAMENTALS OF COMPUTER ORGANIZATION AND ARCHITECTUREShabista Imam FUNDAMENTALS OF COMPUTER ORGANIZATION AND ARCHITECTURE
By : Mostafa Abd-El-Barr & Hesham El-Rewini:: wiley
A complete guidance book
IntroSlides-June-GDG-Cloud-Munich community [email protected]
IntroSlides-June-GDG-Cloud-Munich community [email protected]Luiz Carneiro Introduction slides for starting the June GDG Cloud Munich community gathering in Munich, Germany.
How to Un-Obsolete Your Legacy Keypad Design
How to Un-Obsolete Your Legacy Keypad DesignEpec Engineered Technologies For any number of circumstances, obsolescence risk is ever present in the electronics industry. This is especially true for human-to-machine interface hardware, such as keypads, touchscreens, front panels, bezels, etc. This industry is known for its high mix and low-volume builds, critical design requirements, and high costs to requalify hardware. Because of these reasons, many programs will face end-of-life challenges both at the component level as well as at the supplier level.
Redesigns and qualifications can take months or even years, so proactively managing this risk is the best way to deter this. If an LED is obsolete or a switch vendor has gone out of business, there are options to proceed.
In this webinar, we cover options to redesign and reverse engineer legacy keypad and touchscreen designs.
For more information on our HMI solutions, visit https://www.epectec.com/user-interfaces.
Stay Safe Women Security Android App Project Report.pdf
Stay Safe Women Security Android App Project Report.pdfKamal Acharya Women’s security is a critical issue in today’s world and it’s very much needed for every individual
to be acting over such an issue. This document describes a GPS based “Women Security System''
that provides the combination of GPS devices as well as provide alerts and messages with an
emergency button trigger whenever somebody is in trouble They might not have so much time, all
that they have to do is generate a distress emergency signal by shaking up their phone. Our system
provides a realizable, cost effective solution to problem detection. Nowdays due to recently
happened cases such as rape by drivers or colleagues, burglary etc., women security, especially
women security has become the foremost priority of the world. System uses the Global Positioning
System (GPS) technology to find out the location of women. The information of women's position
provided by the device can be viewed on Google maps using Internet or specialized software. The
companies are looking for-ward to the security problem and require a system that will efficiently
evaluate the problem of women security working in night shifts, traveling alone. We focus on the
proposed model that can be used to deal with the security issue of women using GPS based tracking
systems.
Deep Learning for Natural Language Processing_FDP on 16 June 2025 MITS.pptx
Deep Learning for Natural Language Processing_FDP on 16 June 2025 MITS.pptxresming1 This gives an introduction to how NLP has evolved from the time of World War II till this date through the advances in approaches, architectures and word representations. From rule based approaches, it advanced to statistical approaches. from traditional machine learning algorithms it advanced to deep neural network architectures. Deep neural architectures include recurrent neural networks, long short term memory, gated recurrent units, seq2seq models, encoder decoder models, transformer architecture, upto large language models and vision language models which are multimodal in nature.
International Journal of Advanced Information Technology (IJAIT)
International Journal of Advanced Information Technology (IJAIT)ijait International journal of advanced Information technology (IJAIT) is a bi monthly open access peer-
reviewed journal, will act as a major forum for the presentation of innovative ideas, approaches,
developments, and research projects in the area advanced information technology applications and
services. It will also serve to facilitate the exchange of information between researchers and industry
professionals to discuss the latest issues and advancement in the area of advanced IT. Core areas of
advanced IT and multi-disciplinary and its applications will be covered during the conferences.
Complete University of Calculus :: 2nd edition
Complete University of Calculus :: 2nd editionShabista Imam Master the language of change with the Complete Guidance Book of Calculus—your comprehensive resource for understanding the core concepts and applications of differential and integral calculus. Designed for high school, college, and self-study learners, this book takes a clear, intuitive approach to a subject often considered challenging.
Learning – Types of Machine Learning – Supervised Learning – Unsupervised UNI...
Learning – Types of Machine Learning – Supervised Learning – Unsupervised UNI...23Q95A6706 Learning – Types of Machine Learning – Supervised Learning – Unsupervised Learning- semi supervised learning - The Brain and the Neuron – Design a Learning System – Perspectives and Issues in Machine Learning – Concept Learning Task – Concept Learning as Search – Finding a Maximally Specific Hypothesis – Version Spaces and the Candidate Elimination Algorithm
David Boutry - Mentors Junior Developers
David Boutry - Mentors Junior DevelopersDavid Boutry David Boutry is a Senior Software Engineer in New York with expertise in high-performance data processing and cloud technologies like AWS and Kubernetes. With over eight years in the field, he has led projects that improved system scalability and reduced processing times by 40%. He actively mentors aspiring developers and holds certifications in AWS, Scrum, and Azure.
Modern multi-proposer consensus implementations
Modern multi-proposer consensus implementationsFrançois Garillot Multi-proposer consensus protocols let multiple validators propose blocks in parallel, breaking the single-leader throughput bottleneck of classic designs. Yet the modern multi-proposer consensus implementation has grown a lot since HotStuff. THisworkshop will explore the implementation details of recent advances – DAG-based approaches like Narwhal and Sui’s Mysticeti – and reveal how implementation details translate to real-world performance gains. We focus on the nitty-gritty: how network communication patterns and data handling affect throughput and latency. New techniques such as Turbine-like block propagation (inspired by Solana’s erasure-coded broadcast) and lazy push gossip broadcasting dramatically cut communication overhead. These optimizations aren’t just theoretical – they enable modern blockchains to process over 100,000 transactions per second with finality in mere milliseconds redefining what is possible in decentralized systems.
Abraham Silberschatz-Operating System Concepts (9th,2012.12).pdf
Abraham Silberschatz-Operating System Concepts (9th,2012.12).pdfShabista Imam Complete book of operating system edition 9
Ad
Event Driven Microservices architecture
- 1. Patterns & Practices for Implementing Event-driven Microservices Nikhil Barthwal @nikhilbarthwal [email protected] www.nikhilbarthwal.com
- 2. Agenda (1/2) • Motivations to move from Monolithic to Microservices • Understanding the Distributed Data in Microservices • Using Domain Driven Design for partitioning data • Problems with Distributed Data • Event Driven Microservices 2
- 3. Agenda (2/2) • Communication Patterns for Microservices • Event Sourcing • Command Query Responsibility Segregation • Introducing Sagas • Resources for further reading 3
- 4. Monolithic: The old school approach … • Large code base → Slower development • More time to test & deploy • Too much team interdependency Database Web Service Easy to Develop, Test and Deploy … But doesn’t scale! 4
- 5. Microservices: The Brave new world ... • Smaller code base to understand & change • Autonomous teams • Faster testing & deployment Assembly of Loosely coupled services! Image Source: https://www.slideshare.net/JontheBeach/distributed-sagas-a-protocol-for-coordinating-microservices 5
- 6. Loose Coupling → Distributed Data Database per Service! Faster Innovation! Loosely coupled services Reduces team interdependencies Image Source: http://microservices.io/patterns/microservices.html 6
- 7. How to create service boundaries? An approach to software development for complex needs by connecting the implementation to an evolving model. • Entities • Value Objects • Bounded Context • Aggregates Infrastructure Layer Domain Layer Application Layer User Interface Use Domain Driven Design (DDD)! 7
- 8. DDD: Aggregates • Cluster of domain objects that can be treated as a single unit • One of its component is root • All outside reference would only go to the aggregate root Domain Model = Collection of Aggregates 8
- 9. Data Partition Strategies: Use DDD Aggregates provide boundaries for partition 9
- 10. Problems with Distributed Data • How do we keep data consistent? • How do we query scattered data? 10
- 11. Cannot use ACID Transactions BEGIN TRANSACTION SELECT ADDRESS FROM CUSTOMERS WHERE CUSTOMER_ID = XXX SELECT PRICE FROM PRODUCTS WHERE CUSTOMER_ID = YYY INSERT INTO ORDERS ... COMMIT TRANSACTION Private to Customer service Private to Product service 11
- 12. Cannot use 2-Phase Commit • Coordinator is a single point of failure • Very chatty, with O(4n) messages, O(n2) with retries • Locks would decrease throughputs • Impacts availability (CAP theorem limitations) Guarantees consistency, but … 12
- 13. Consistency Eventual Consistency Availability Partition (Network) Eventual Consistency Use Event Driven Microservice Architecture! 13
- 14. Event Driven Architecture • Event occurs when a change happens in system • All listeners get notified of the event, may take action • Highly distributed/loosely coupled architecture • Often used for asynchronous flows of information 14
- 15. Communication: Direct Messaging Benefits: • Easier implementation • Better Error control Drawbacks: • Increased coupling • Difficult to scale Order Service Product Service Customer Service Fulfillment Service Payment Service Shipping Service 15
- 16. Communication: Via Message broker Benefits: • More scalable • Increased Decoupling Drawbacks: • Requires Broker as Highly Available component Order Service Product Service Customer Service Fulfillment Service Payment Service Shipping Service Message Broker 16
- 17. Communication Patterns Request/Response (synchronous) Event-Driven (asynchronous) Tier-3: Little to No impact for Customer Tier-2: Impacting Customers indirectly Tier-1: Directly Customer facing 17
- 18. Event Sourcing: Introduction • Modeling state changes as sequence of events • Storing the event that could trigger the state change • Enables rolling back to particular time in history Examples: 18
- 19. Event Sourcing: Snapshots Alternative to playing events: Snapshots 19
- 20. Event Sourcing: Multiple views Image Source: https://www.confluent.io/wp-content/uploads/2016/09/Event-sourced-based-architecture.jpeg Adding applications that process event … but create a different view! 20
- 21. Event Sourcing: Benefits & Drawbacks Benefits: • 100% accurate audit logging • Easy temporal queries • Applications can process same events but create views Drawbacks: • Adds Complexity • No Strict Consistency • Longer bootup times (Snapshots can help) 21
- 22. Command Query Responsibility Segregation CQRS Pattern Must for Event Sourcing! Read Write Image Source: https://martinfowler.com/bliki/CQRS.html 22
- 23. CQRS: Benefits & Drawbacks Benefits: • Needed for Event Sourcing • Improved separation of concerns • Supports scalable multiple denormalized views Drawbacks: • Increased complexity • Potential code duplication • Replication lag as No Strict Consistency 23
- 24. Sagas: Introduction • Based on a 1987 paper • Initially for a single database running on one node • Now adapted for distributed systems with asynchrony and partial failure 24
- 25. Transaction & Rollback Transaction • Every Transaction has a Rollback transaction • This logic must be included in the service T1 T2 T3 R1 R2 R3 Transactions → Rollback Transactions → 25
- 26. Sagas: Example This action initiates the saga Check Credit Service Withdrawal Service Deposit Service Deposit Check Long running transactions … use compensating actions to handle failures! Does Sender have enough money in his account? Withdraw the money (unless it is on hold)? Deposit the money (unless account is deactivated)? 26
- 27. Resources • Using DDD to develop Microservices: https://www.infoq.com/news/2016/02/ddd- microservices • Overview of Saga Pattern: http://microservices.io/patterns/data/saga.html • Distributed Sagas: https://www.slideshare.net/JontheBeach/distributed-sagas-a- protocol-for-coordinating-microservices 27
- 28. Summary • Microservices enable faster innovation • DDD can used to define service boundaries • Data is distributed which create challenges • Use Event Driven Architecture for eventual consistency • Understand Event Sourcing & CQRS • Use Sagas to maintain data consistency across services 28