Please enable JavaScript.
Coggle requires JavaScript to display documents.
IT ARCHITECTURE, Constrains, Shapes - Coggle Diagram
IT ARCHITECTURE
Data Architecture
How firm's data assets are organized
Causes
Geographic dispersion
Solution
Partitioning
Can slice the app's database into smaller pieces, where each piece only keeps data for the locale.
Replication
Making copies of an app's entire data and keep a copy at each location so users' apps make a quick local trip to access. To ensure that the copies remain synced, connect them using the Internet.
Fragmented across apps
All apps collectively determine how a firm's data assets are organized and where they are located.
Data warehouses assemble copies of data to integrate siloed data
App Architecture
How an app is divvyed between a user's device and more powerful "server" machine
Client-Server architecture
Centralizes only data, clients do heavy lifting
Most common in corporate portfolio, predates cloud
Costlier if custom-built
Burdensome upgrades
Offers more potential for competitive differentiation
Peer-to-Peer architecture
No central server to every client performs all app function
Recommended only for scale-hungry apps that demand to control
Cloud architecture
All heavy lifting is done on the server side via the "cloud" (e.g., Siri)
IT Architecture
A blueprint of IT assets in the IT portfolio describing what they do and how they interact
3 Classes of IT Assets
Data
Apps
IT infrastructure
Enterprise IT architecture
Complexity manageable by
Increasing the autonomy of IT assets
Easing integration
Key Idea : Lump things together that change for some reasons and at similar speed. Apps and infrastructure do not need to change at the same speed.
E.g., Like a clock's two hands - at two speeds : apps that change faster to foster business agility and infrastructure that changes slower to lower cost.
Constrains
Shapes