Please enable JavaScript.
Coggle requires JavaScript to display documents.
IT ARCHITECTURE - Coggle Diagram
IT ARCHITECTURE
LAYER #2 APP ARCHITECTURE
Apps are software programs that undergird the functionality of a hardware device
Interaction functionality, which handles an app’s interaction with users (such as receiving inputs and displaying outputs)
App logic, which performs the core work that makes the app useful to its users; most business innovation occurs in this block
Data storage, for data that an app uses and produces
An app’s architecture is simply how you choose to divide these three pieces between a centralized “server” and user devices
Cloud architecture is a reincarnation of mainframe architectures from the 1960s
The strength and weakness of cloud architecture is that it centralizes everything
Centralization generates economies of scale, eases maintenance (only the software on the server side needs upgrading, not individual devices)
Cloud architectures are therefore recommended as a capital-economizing approach for apps that do not differentiate your firm
Client-server app architecture—which predates cloud architectures—locates the interaction and app logic functions on user devices and centralizes only data storage
Peer-to-peer app architecture takes the stand-alone architecture and then connects all user devices using the Internet
LAYER #1 IT INFRASTRUCTURE ARCHITECTURE
firm-wide and digital plumbing shared IT assets and IT services used by all line functions
data travels and apps are linked and the hardware on which apps run and store data
relatively stable, generic commodity and rarely competitive differentiator
firm-wide IT infrastructure improve how fast and inexpensively new apps can be implemented
multiplying the payoffs from systematically separating infrastructure from apps
the key- how much to decentralize IT infrasturcture or how much to centralize
centralize create firm-wide economies of scale by aggregating the IT infrastructure structure demand
decentralization facilitates tailoring it to individual line functions' unique needs
hybrid mix (which decentralize some but centralizes other IT infrastructure)
Non-IT managers can contribute answers to two questions about IT infrastruc-ture
is firm-wide economy or tailoring to line functions more important
what is considered “good enough” operational performance for their line func-tions? (Higher performing IT infrastructure costs more.)
LAYER #3 DATA ARCHITECTURE
Integrated firm-wide data is the foundation of IT-enabled automation of business processes and large-scale business analytics
the prevalent problem in firms is prolifera-tion of duplicated and inconsistent data
Two cause : fragmented across apps and geographic dispersion
fragmentd across apps
app architecture is for individual apps
Every app has its own central server, and their multitude can create silos of data scattered across different 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 intergrate siloed data
geograhic dispersion
To pick appropriate data architectures, non-IT managers must decide
what data should be centralized firmwide for executing your core business proceses or for analytics?
what data must be shared across your markets?