Model

x-axis: horizontal duplication scale by cloning eg. load-balander + auto-scaling y-axis: functional decomposition scale by splitting different things eg. monolith -> microservices (compare with Model_ 5 service disintegrators #3 scalability and throughput) z-axis: data partitioning scale by splitting similar things “sharding” eg. split data per product-id (shard 1 = product-id 0 - 99, shard 2 = product-id 100 - 199, …) eg. split data per time (aka “archiving older data”)...

Granularity integrators (1) database transactions (2) data dependencies (3) workflow and choreography fault tolerance responsiveness and performance (Model_ 3 types of latency) reliability & data consistency (2) data dependencies axiom: service that writes data, owns it big ball of distributed mud (3) workflow and choreography a) fault tolerance dependency on other service over the network? network problems breaks your service (monolith did not have this problem) b) responsiveness and performance !...

subjective: (1) service functionality: single responsibility measurable: (2) code volatility: how often does code change (3) scalability and throughput: scale/throughput, startup delay (4) fault tolerance: continue working if one part crashes (5) access control: separate sensitive data to a separate service (1) service functionality what is “single responsibility” is subjective… (2) code volatility (3) scalability and throughput scalability (requests / minute) startup time “mean time to startup (service)” !...

(compare with Model_ AWS Cloud Value Framework) (compare with Model_ Cloud Computing benefits) agility: innovate faster elasticity: no need to overprovision cost savings: trade capital expenses for variable expenses global: deploy globally in minutes

operations security software infrastructure

business business people governance technical platform security operations

operational excellence security reliability performance efficiency cost optimization sustainability

re-host = lift&shift re-platform = tinker + lift&shift re-factor/re-architect re-purchase = not move it, just buy it anew retain = leave as is retire = stop using it server -> EC2 network -> VPC driven by business needs (new features / dev speed)

(compare with Model_ AWS Cloud Value Framework) (compare with Model_ 4 benefits of cloud computing) Cloud Computing Benefits variable expenses (vs upfront expenses) cost optimization (don’t invest in maintaining data centers) capacity (peak use vs rest of year) economies of scale (AWS buys a lot, can get that cheaper) Speed and agility (time between wanting resources vs having resources) Global in minutes (1) variable expenses upfront expenses - invest before using variable expenses - pay what you use (2) cost optimization invest...

cloud deployment on-premise deployment hybrid deployment (1) cloud deployment run full app in the cloud migrate to the cloud build new apps (2) on-premise deployment use virtualization and resource management tools to deploy resources use app management and virtualization to increase resource usage (3) hybrid deployment connect cloud with on-premise integrate cloud with legacy