Please enable JavaScript.
Coggle requires JavaScript to display documents.
IT ARCHITECTURE - Coggle Diagram
IT ARCHITECTURE
CORPORATE IT'S
Most firms obsess over initial spending that first dollar wisely :check:
Yet they overlook how today’s IT choices hurt their strategy later
IT architecture
=
technological DNA
: Irreversible and preordaining
Predicates evolvability before first line of code is written
Consequences:
Operational and strategic
THREE ARRANGEMENTS - APP ARCHITECTURES
2) Client-server architecture
Most common in corporate portfolios; predates cloud
Burdensome upgrades
Costlier if custom-built
Offers more potential for competitive differentiation
3) 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
Infinite, dirt-cheap scalability
Zero control over user devices relegates it to niche, eclectic uses
1) Cloud architecture
Clients can be feeble & cheap
Low upfront costs ~ utility-like model
Easy maintenance
GOOD ARCHITECTURE
Balances economical performance today and economical changeability later
Fulfils today’s requirements but plans for tomorrow’s expectations
DEFINITION:
A blueprint of IT assets in your IT portfolio describing
what they do and how they interact
Enterprise architecture:
How a firm’s corporate IT apps,
infrastructure, and data are organized
App architecture:
How an app is divvyed between a user’s device
and a more powerful “server” machine
Data architecture:
How your firm’s data assets are organized