Please enable JavaScript.

Coggle requires JavaScript to display documents.

Architecture Software - Coggle Diagram

- - - - Terraform
        
        State management : this is the json data (file) that terraform use store data/state of the infrastructure in order to regcozine what is the change.
        Should use remote state manage file with blocking to make sure there is only 1 active terraform apply running to avoid collapse
        
        Modules
        
        Like the application code, for core modules,securiry,utility... should package as module to reuse and governance
        
        CICD to manage deployment
        
        Dev commit change in terraform
        
        Use Codepipeline to check the commit --> Terraform plan to see the change
        
        Senior dev review and approve the change
        
        Codepipeline to authenticate, authorize and run terraform apply to apply the change to production
    - - Every modules should use infrastructure as code to achieve consistency
      - Deploying using CICD to make sure blueprints always sync and available and can deploy in different regions
  - - - Frontend Federation :
        
        supported from Webpack 5 , allow host application can share library to remote apps
      - Authen
        
        Can use centralize Authenticatie service like Auth0 to mange and create JWT application
      - Authorization
        
        JWT role base / permission base approach
        
        refresh token
      - Shared data between frontend applications
        
        Shared data via state ( pass when init call/moduel)
        
        Shared via URL
        
        Shared via manage state framework (as Redux)
        
        Browser events
- - - - What does this system do ? (eg user has to be able to upload a video ? system must process payment..)
        Be specific
    - - scalability
        
        How will the system need to handle growth ? 1000 user today ? 1 million users next year ?
      - security
      - availability
        
        if the system allow to down sometime (99.99% up) or need to be online all the time (99.9999%) like phone network
      - latency
        
        How's fast the response should be ? for a trade system the response time must be million seconds and it will different with a nightly report generator that accepts hours
      - Consistency
        
        If I write a data to system, Do I see that with next read immediately (strong consistency) or slightly delays is ok
- - - - Functional Requirements
        
        real time not for B2B corporate client
        
        type notifications : large incoming fund transfer , trade document approvals , security issues
      - Non Functional requirements
        
        Availability : need 99.99% available
        
        Consistency : make sure corp clients always receive notifications when transactions happened , not duplicated notifications
        
        latency : less than 500ms
        
        z
        
        scalability : assume number of corporate clients (including merchants, SMEs...) is 1mil and regular get notifications 30 times/months
        
        Sequencing : send by order
      - Assumptions: assume number of corporate clients (including merchants, SMEs...) is 1mil and regular get notifications 30 times/months ==> average 13 noti/seconds