Please enable JavaScript.

Coggle requires JavaScript to display documents.

CHAPTER 3 - Coggle Diagram

- - - - Peer-to-Peer Architecture
        
        infinite, dirt cheap scalability
        
        zero control over user devices relegates it to niche, eclectic uses
        
        strength in numbers
        
        no central server- every client performs all app functions
        
        (interaction, app logic, data storage)-INTERNET(use)
      - Client-Server Architecture
        
        CLIENTS(interaction, app logic)-INTERNET-SERVER(data storage)
        
        offers more potential for competitive differentiation
        
        costlier (if custom built $15-$40 per line + 700% maintenance)
        
        two newer cloud-inspired variants enable building cheaper, faster custom apps
        
        service-oriented architectures
        
        some server-side functionality purchased as a service, integrated into custom apps
        
        Micro-services
        
        many discrete generic services cobbled into an app's logic
        
        burdensome upgrades
      - Cloud Architecture
        
        low upfront costs - utility-like models
        
        easy maintenance - only a central copy needs updating
        
        centralizes everything
        
        ongoing, variable operating costs replace upfront costs
        
        a single point of vulnerability
        
        strategically undifferentiating
        
        clients can be feeble & cheap - only input display information
        
        all heavy is done on the server side via the 'cloud'
        
        CLIENTS-INTERNET-SERVER (interaction, app logic, data server)
  - - - networks: data travels & apps are linked
      - hardware: apps run and store data
        
        eg: computers, tablets, servers & storage devices