Please enable JavaScript.

Coggle requires JavaScript to display documents.

SA_3_DesignPrincipls - Coggle Diagram

- - - - Broker
        
        client -> proxy -> broker -> proxy -> server - Relationships
        
        client and server can only attach to broker - Constrains
        
        Client, server, broker, proxy for both side - Elements
        
        Weeknesses
        
        broker - single point of failure
        
        difficult to test
        
        latency
        
        add complexity
        
        Separate users from client via broker. Broker mediates the connection - Overview
      - Pipe and Filter patterns
        
        pipes connects with filter and again -Relationships
        
        Constrains
        
        data types should be known betweeen filters
        
        Elements
        
        filter - transform data
        
        pipe - move data
        
        Weeknesses
        
        filters connected by pipes, have input and output - Overview
      - Layered
        
        allowed to use - Relationships
        
        Constrains
        
        at least twi layers
        
        relationshipps should not be circular
        
        Every pease allocated to one layer
        
        layers - Elements
        
        Weeknesses
        
        add new layer - new costs
        
        performance to go thrue the layers
        
        defines layers- Overview
      - Messaging pattern
        
        Problem
        
        need to provider "middle man" as services can be in different context
        
        Solution
        
        communicate via service bus to have async connection. Like kafka - sender send to service bus, reader read from service bus and vise verse.
        
        Context
        
        few services developer independently
        
        need low coherent reliable communication, but without tight dependency
      - Publisher Subscriber pattern
        
        Problem
        
        notification mechanism should not couple components
        
        Solution
        
        Notify subscribers interested in this events via middle component. Each publisher and subscriberes should register and than notify in middle "Change Propagator"
        
        Context
        
        need to inform other component aout state change from another
      - Dynemic Router
        
        also messaging pattern, but mediator based on registered rules.This rules can be changed danemicly