Please enable JavaScript.
Coggle requires JavaScript to display documents.
SUMMARY CHAPTER 3 (ARCHITECTURE) - Coggle Diagram
SUMMARY CHAPTER 3 (ARCHITECTURE)
APPS ARCHITECTURE
Apps are software programs that undergird the functionality of a hardware device such as PC, smartphone, tablet, cash register, or other Internet-connected devices such as camera or car system. Such devices (called clients) are used to access a resource or service placed on a more powerful central computer (called a server). One server machine can serve many user devices, which connect to it through the internet.
App Architecture
= choosing where to locate the three pieces (like arranging pieces on a chessboard)
The three Arrangements of App Architectures
Client-server architecture
Peer-to-peer architecture
No central server (every client performs all app functions)
Every client simultaneously acts as a little server for all other clients (-strength in numbers; every new client increases the hive's collective capacity.)
Infinite, dirt-cheap scalability :check:
Zero control over user devices relegates it to niche :red_cross:
Centralize only data; clients do heavy lifting.... Most common in corporate portfolios: predates cloud
Offers more potential for competitive differentiation :check:
Costlier, Burdensome upgrades :red_cross:
Two newer cloud-inspired variants enable building cheaper, faster custom apps (1. Service-oriented architectures 2. Micro-services)
Cloud architecture
All heavy lifting is done on the server side via the "cloud" (e.g., Siri).
Clients can be feeble and cheap (only input and display information)... reincarnation of 1960s mainframe architecture
centralize everything, easy maintenance, low upfront cost :check:
Ongoing, variable operating costs, A single point of vulnerability and strategically undifferentiating :red_cross:
Has irreversible operational and strategic consequences.
DATA ARCHITECTURE
Data architecture determines data consistency and accessibility
integrated firmwide data is the foundation for automation and analytics ..... widespread problem (Proliferation of duplicated, inconsistent data)
Causes
1. Fragmented across apps (app architecture is for individual apps)
All apps collectively determine how a firm's data assets are organized and where they are located
Data warehouse assemble copies of data to integrate siloed data
2. Geographic dispersion
to pick appropriate data architectures, non-IT managers must decide:
What data should be centralized firmwide for executing your core business processes or for analytics?
What data must be shared across your markets?
IT INFRASTRUCTURE ARCHITECTURE
Firmwide digital plumbing used by all line functions and apps
@ IT infrastructure architecture is their firmwide arrangement
@ Relatively stable, generic commodity, and rarely a competitive differentiator
Must be reliable but economical
Consumes over 50% of corporate IT budgets
Non-IT contributions
Is frugality of tailoring more important for their units
Define "good enough" operational performance?
Centralized
= +Scale economies :check: +Firmwide integrations :check: +Concentrates vulnerability :red_cross:
Decentralized = +Increase costs :red_cross: +Tailoring to line functions :check: +Widespread vulnerability :red_cross:
