Please enable JavaScript.

Coggle requires JavaScript to display documents.

Scaling a System, Full Stack Development, Types of Architecture,…

- - - - Docker
      - Kubernetes
      - Container Orchestration Platforms
        
        EKS
  - - - PostgreSQL
      - MySQL
      - Microsoft SQl Server
      - Oracle
        
        Activities
        
        Stored Procedures
        
        Triggeers
        
        SQL Queries
        
        DB Products
        
        Oracle 9i
        
        Oracle PL/SQL
    - - Cassandra
      - MongoDB
      - RavenDB
      - CouchDB
      - DynamoDB
  - - - Scripting Technologies
        
        Bash
        
        Scheduling
        
        Job Scheduling
        
        Automatic Batch Jobs
        
        Forking/Cloning Jobs
  - - - Logstash
      - Kibana
      - ElasticSearch
  - - - JIRA
      - BugZilla
- - - - Jenkins
      - Travis
      - Containerised Technologies
        
        Docker
        
        Kubernetes
        
        Container Orchestration Platforms
        
        EKS
- - - - How?
        If logic is dependent on other service features?
        
        Communication strategies between services
        
        Sync:
        using direct requests
        
        Pros
        
        easy concept to understand
        
        Need not require personal DB
        
        Cons
        
        Dependency on other services
        
        One service fails, it fails
        
        slowest service request among all requests is its fastest reponse time
        
        web of requests
        
        Async:
        using events
        
        Only Event based communication
        
        type
        
        data
        
        All cons from Sync based communication
        
        Event Based Communication + Every Service with Personal DB (Microservice - database-per-service pattern)
        (Requests per service is updated to their service only and not updated to the other services, hence we require event bus to be notified to the other services which are looking to it)
        
        Pros
        
        No Dependency on other DB
        
        its response is fast
        
        Cons
        
        Data Duplication. (Maybe extra storage price, but its fine and worth it.)
        
        Concept harder to understand
    - - Database-Per-Service
        
        Database/Schema might change unexpectedly
        
        Each service should run independently
        
        Scaling Wastage
        
        No other service's DB dependency
        
        Single Point of Failure
        
        Some service might function more efficiently
        with different DB types - NoSql, RDBMS etc