Basics - 1

Wednesday, December 07, 2016 10:17 AM

1. Business Drivers
a. Capacity Planning
i. Lead Strategy
ii. Lag Strategy
iii. Match Strategy
b. Cost Reduction
i. Fixed cost = of acquiring new infrastructure
ii. Variable cost = of maintaining it
iii. Overhead cost like training etc.
c. Organizational agility
d. Technical Innovation
i. Clustering
1) Grid Computing
2) Virtualization
ii. Cloud Enabling Technologies
1) Broadband network & internet
2) Data center technologies
3) Modern Virtualization technologies
4) Web technologies
5) Multitenant technologies
6) Service technologies
2. Basic Terms
a. Cloud
b. IT resource (physical or virtual)
c. On premise
d. Cloud consumer and cloud provider
e. Scaling
i. Horizontal scaling - scaling out and scaling in
ii. Vertical scaling - scaling up and scaling down
f. Cloud service
g. Cloud service consumer
3. Goals and Benefits of cloud
a. Reduced investment and proportional cost
b. Increased scalability
c. Increased availability and reliability
4. Risk and Challenges
a. Increased security vulnerability
b. Reduced operational governance control
c. Limited probability between cloud providers
d. Multi regional compliance and legal issues
5. Roles and Boundaries
a. Cloud Provider
b. Cloud consumer
c. Cloud service owner
d. Cloud resource admin
e. Organizational boundary (trust boundary)
6. Cloud characteristics
a. On demand usage
b. Ubiquitous access (widely accessible)

New Section 1 Page 1

 b. Ubiquitous access (widely accessible)
c. Multi-tenancy and resource pooling
d. Elasticity
e. Measured Usage
f. Resiliency
7. Cloud Delivery Models
a. Infrastructure as a service (IaaS)
b. Platform as a service (PaaS)
c. Software as a service (SaaS)
8. Cloud Deployment Methods
a. Public Clouds
b. Community Clouds
c. Private clouds
d. Hybrid clouds etc.

New Section 1 Page 2

Basics - 2
Friday, December 09, 2016 4:41 PM

1. Cloud Enabling Technologies

a. Broadband network and Internet
i. Architecture
ii. Internet service providers (ISP)
iii. Connectionless packet switching
iv. Router based interconnectivity
v. Technical and business considerations
1) Connectivity issues
2) Network bandwidth and latency issues
3) Cloud carrier and cloud provider selection
b. Data Center technology
i. Virtualization
ii. Standardization and modularity
iii. Automation
iv. Remote operation and management
v. High availability
vi. Secure design, operation and management
vii. Computing hardware like blade server technology
viii. Storage hardware
1) Hard disk arrays
2) Hot - swappable hard drives
3) Storage visualization
4) Fast data replication mechanism
5) Network storage
a) Storage area network (SAN)
b) Network attached storage (NAS)
ix. Network hardware
1) Carrier and external network interconnection
2) Web tier load balancing and accelearation
3) LAN Fabric
4) SAN fabric
5) NAS gateways
c. Virtualization technology
i. Hypervisor (VM monitor)
ii. Hardware independence
iii. Server consolidation
iv. Resource replication
v. Operating system based virtualization
vi. Hardware based virtualization
vii. Virtualization infrastructure management
viii. Other considerations
1) Performance overhead
2) Special hardware compatibility
3) Portability
d. Web technology
i. Basic web technology (browser and web server)
1) Uniform resource locator (URL)
2) Hypertext transfer protocol (HTTP)
3) Markup languages (HTML, XML)

New Section 1 Page 3

 3) Markup languages (HTML, XML)
ii. Web Apps
e. Multitenant technology
i. Usage isolation
ii. Data security
iii. Recovery
iv. Application upgrades
v. Scalability
vi. Metered usage
vii. Data tier isolation
f. Service technology
i. Web services
1) Web services Description Language (WSDL)
2) XML schema definition language
3) Universal Description, discovery and integration (UDDI)
ii. REST services
1) Client server
2) Stateless
3) Cache
4) Interface / uniform contract
5) Layered system
6) Code on demand
iii. Service Agents
iv. Service middleware
1) Enterprise service bus (ESB)
2) Orchestration platform
2. Fundamental Cloud Security
a. Basis terms
i. Confidentiality
ii. Integrity
iii. Authenticity
iv. Threat
v. Vulnerabilities
vi. Risk
vii. Security controls
viii. Security mechanisms and policies
b. Threat agents
i. Anonymous attacker
ii. Malicious service agent
iii. Trusted attackers
iv. Malicious insider
c. Cloud security threats
i. Traffic eavesdropping
ii. Malicious intermediary
iii. Denial of service
iv. Insufficient (Weak) authentication
v. Virtualization attack
vi. Overlapping trust boundaries
d. Additional considerations
i. Flawed implementation
ii. Security policy disparity
iii. Contracts and SLAs
iv. Risk management (assessment, treatment and control)

New Section 1 Page 4

Basics - 3
Friday, December 09, 2016 4:56 PM

1. Cloud Infrastructure Mechanism

a. Logical network perimeter
i. Virtual firewall
ii. Virtual network
b. Virtual server
c. Cloud storage devices
i. Network storage interfaces
ii. Object storage interfaces
iii. Database storage interfaces
d. Cloud usage monitor
i. Monitoring agent
ii. Resource agent
iii. Polling agent
e. Resource replication
f. Readymade environment
i. Software development kit (SDK)
2. Specialized cloud mechanisms
a. Automated scaling listener
i. Automatically scaling IT resources
ii. Automatic notification
b. Load Balancers
i. Workload distribution
1) Asymmetric distribution
2) Workload prioritization
3) Content - aware distribution
ii. Can exist as
1) Multilayer network switch
2) Dedicated hardware appliance
3) Dedicated software system
4) Service agent
c. SLA Monitors
d. Pay per use monitor
i. Request / response message quantity
ii. Transmitted data volume
iii. Bandwidth consumption
e. Audit monitor
f. Failover system
i. Active active
ii. Active passive
g. Hypervisor
h. Resource cluster
i. Server cluster
ii. Database cluster
iii. Large dataset cluster
iv. 2 basic types
1) Load balancer cluster
2) High availability cluster
i. Multi device broker
i. Has:
1) XML gateway

New Section 1 Page 5

 1) XML gateway
2) Cloud storage gateway
3) Mobile device gateway
j. State management databases

New Section 1 Page 6

Basics - 4
Tuesday, December 13, 2016 1:35 PM

1. Cloud management mechanism

a. Remote administration system
i. 2 main types of portals:
1) Usage and administration portal
2) Self-service portal
b. Resource management system
i. Virtual infrastructure manager (VIM)
c. SLA management system
d. Billing management system
2. Cloud security mechanism
a. Encryption
i. Symmetric (secret key cryptography)
ii. Asymmetric (Public key cryptography)
b. Hashing
c. Digital signatures
d. Public key infrastructure (PKI)
e. Identity and access management
i. Authentication
ii. Authorization
iii. User management
iv. Credential management
f. Single sign on (SSO) mechanism
g. Cloud based security groups
h. Hardened virtual server images
3. Fundamental cloud architectures
a. Workload distribution architectures
i. Service load balancing architectures
ii. Load balanced virtual server architecture
iii. Load balanced virtual switches
b. Resource pooling architecture
i. Physical resource pools
ii. Virtual resource pools
iii. Storage pools
iv. Network pools
v. CPU pools
c. Dynamic stability architecture
i. Dynamic horizontal scaling
ii. Dynamic vertical scaling
iii. Dynamic relocation
d. Elastic resource capability architecture
e. Service load balancing architecture
f. Cloud bursting architecture
g. Elastic risk provisioning architecture
h. Redundant storage architecture

New Section 1 Page 7

API (Application Programming Interface)
Thursday, December 22, 2016 1:53 PM

1. API is:
a. A contract that increases confidence
b. Not a website as websites don't have contracts
c. But, APIs and Websites have a lot in common
i. Can get updated like website without 'breaking' the clients
d. Of 2 types (based on formality of business arrangement):
i. Private
ii. Public
e. Why we are talking about it now?
i. Process maturity: offers common platform to collaborate
ii. Self-service: thriving online communities
iii. Technological maturity: rise in API traffic; consumers moving away from browser
based consumption model to app based model on mobile devices
2. The API value chain:

a.

3. API business models for working with partners

a. Expanding reach: More apps, more platforms: you work on frontend, I will work on backend.
b. Gaining indirect revenue
c. Increasing innovation through partners
d. Increasing application value through integration: 'glue' of SaaS
e. Freemium use: Offer a level of free access and enforce the conditions that trigger payment

New Section 1 Page 8

 f.

i. CPA = Cost per action

ii. CPC = cost per click
iii. Internal ROI happens when an API serves a useful purpose inside an organization
iv. Content acquisition = API providing valuable information to the API provider
4. An API team:

New Section 1 Page 9

 a.

5. Technology recommendation for APIs:

a. REST: for the structure - easier to learn, consume and expand than others like SOAP.
b. JSON: for the data format that the API consumers and returns
c. Oauth: for security
6. REST
a. Representational State Transfer
b. Based on HTTP standard - GET (read), POST (create), PUT (update) and DELETE
c. URI: Uniform resource identifier on the internet

d.

e. XML vs JSON (JavaScript Object Notation)

i. JSON can easily interface with web and mobile apps, more compact than XML
7. Try to change API versions as rarely as possible

New Section 1 Page 10

7. Try to change API versions as rarely as possible

New Section 1 Page 11