Scribd Logo
Upload

Welcome to Scribd!

  • S2 Slides

    Uploaded by

    CJ Ho
    5 views11 pages
    Microservices architecture emerged to address limitations of monolithic architecture and service-oriented architecture (SOA). Monolithic architecture tightly couples all components within a single process, hindering scalability, while SOA, though allowing component distribution, introduced complexity through enterprise service buses and rigid service contracts. Microservices break applications into small, independent components that communicate over well-defined interfaces, aiming for agility, scalability and continuous delivery of large, complex applications.

    Original Description:

    Original Title

    S2_Slides

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    Microservices architecture emerged to address limitations of monolithic architecture and service-oriented architecture (SOA). Monolithic architecture tightly couples all components within a single process, hindering scalability, while SOA, though allowing component distribution, introduced complexity through enterprise service buses and rigid service contracts. Microservices break applications into small, independent components that communicate over well-defined interfaces, aiming for agility, scalability and continuous delivery of large, complex applications.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    5 views11 pages

    S2 Slides

    Uploaded by

    CJ Ho
    Microservices architecture emerged to address limitations of monolithic architecture and service-oriented architecture (SOA). Monolithic architecture tightly couples all components within a single process, hindering scalability, while SOA, though allowing component distribution, introduced complexity through enterprise service buses and rigid service contracts. Microservices break applications into small, independent components that communicate over well-defined interfaces, aiming for agility, scalability and continuous delivery of large, complex applications.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 11

    History of

    Microservices

    Memi Lavi
    www.memilavi.com
    Microservices are a result of problems with
    two architecture paradigms:
    - Monolith
    - SOA
    Monolith
    Monolith Architecture

    • The original architecture

    • All software components are executed in a single process

    • No distribution of any kind

    • Strong coupling between all classes

    • Usually implemented as Silo


    Monolith Architecture - Example
    HR App

    Sometimes

    Process

    DB Sometimes
    Monolith Architecture - Example
    HR App Purchasing App

    X
    DB DB
    Monolith Architecture Pros

    • Easier to design

    • Performance
    SOA
    (Service Oriented Architecture)
    Service Oriented Architecture

    • First coined in 1998

    • Apps are services exposing functionality to the outside world

    • Services expose metadata to declare their functionality

    • Usually implemented using SOAP & WSDL

    • Usually implemented with ESB


    SOA Architecture - Example
    HR Service Purchasing Service

    Enterprise Service Bus


    SOAP SOAP

    DB DB
    SOA Pros

    • Sharing Data & Functionality

    • Polyglot Between Services

    You might also like